Linking.Release Skipped When Building Previously Cached Files

[jteppinette]

Version

v2.6.9+202207181016

Operating System Version and Architecture

macOS 12.4 M1

Describe Bug

If you run xmake build on a file which has already been compiled, then the linking.release step is skipped. Therefore, the new binary is not created. This results in the previous binary being used during xmake run.

main.cpp - v1

#include <iostream>

int main() {
  std::cout << 1 << std::endl;
}

xmake.lua

target("main")
    set_kind("binary")
    set_languages("cxx17")
    add_files("main.cpp")

build - v1

$ xmake; xmake run 
[ 25%]: ccache compiling.release main.cpp
[ 50%]: linking.release main
[100%]: build ok!
1

main.cpp - v2

#include <iostream>

int main() {
  std::cout << 2 << std::endl;
}

build - v2

$ xmake; xmake run 
[ 25%]: ccache compiling.release main.cpp
[ 50%]: linking.release main
[100%]: build ok!
2

main.cpp - v1

#include <iostream>

int main() {
  std::cout << 1 << std::endl;
}

build - v1

$ xmake; xmake run 
[ 25%]: ccache compiling.release main.cpp
[100%]: build ok!
2

Notice, above, the linking.release stage was skipped and the resulting binary wrote 2 instead of 1 to the console.

Temporary Resolution

I was able to remediate this issue by disabling the build cache:

xmake.lua

set_policy("build.ccache", false)

target("main")
    set_kind("binary")
    set_languages("cxx17")
    add_files("main.cpp")

[waruqi]

? I don't understand what you mean.

[jteppinette]

@waruqi I have written about the issue in more detail after digging in a little more. I isolated the issue to the build cache.

[waruqi]

I have fixed it in previous issue. #2620

please update to dev and try it again.

xmke update dev

[jteppinette]

Thanks!