Comment by ~lattis on ~lattis/muon
Changed to pass
-print-search-dirs
. ~xvilka, can you confirm this fixes the tcc issue?
Comment by ~lattis on ~lattis/muon
REPORTED
RESOLVED NOT_OUR_BUGComment by ~lattis on ~lattis/muon
REPORTED
RESOLVED CLOSEDComment by ~lattis on ~lattis/muon
~firasuke, did you test the latest master? It should now work even with .. in the path.
Ticket created by ~lattis on ~lattis/muon
.S files are internally handled as a separate language.
In meson, they are treated the same as either C or C++ if there are no C sources. This means that in meson c_args gets applied to .S files, while in muon it does not.
Comment by ~lattis on ~lattis/muon
Okay, so at this point I'm a little confused what this thread is about. libucontext works fine for me. I am going to make another todo about .S files not getting correct arguments. If you have another issue that is hopefully more specific, feel free to create a new todo.
REPORTED
RESOLVED CLOSEDComment by ~lattis on ~lattis/muon
REPORTED
RESOLVED CLOSEDComment by ~lattis on ~lattis/muon
This issue should be fixed in 34953adc.
As to why you need to use
muon -C ../build_dir install
, this is because muon does not create a build target named install to run this command for you. When using meson, allsamu -C ../build_dir install
does is runmeson install -C ../build_dir
for you. In general, it is better to run the command yourself since you then can pass arguments, so I omitted the shorthand version from muon. There is also the worry of accidentally running samu with superuser privileges causing it to corrupt the build directory.