Alexander Bothe
Alexander Bothe
(Ah, well, yes, just linking in some dedicated object files is still making sense though!)
I think these couple of lines will already do it - you just have to put a link to your lib/a/obj/o-Files into the project, make them "Compile" as build action,...
I honestly don't want to change any GUI for getting this feature implemented.
Concerning the lib.exe merge command, you may always put in a pre-build-command in your project configuration. :)
It should work as well when building shared or static libraries since the same procedures are used for these build types as well.
segfault? So we found another dmd bug! :stuck_out_tongue: Please excuse my sunday-driven laziness, but as the most appropriate solution right now I recommend tweaking the "linker" executable and debug/release arguments...
The reason I chose dmd for linking static libs was the different default lib tool on windows and linux/osx -- I didn't want to extend the option matrix any further.
> This doesn't work either, because Mono-D still passes the static lib to dmd How about removing `$libs` from the linker arguments? In the target executable, the third party libs...
`-gc $sources $includes -lib "-od$objectsDirectory" "-of$lib" -w -vcolumns` It already is not taking any libs, but in your log > dmd -debug -gc "test.a" "test.d" "-Iusr/share/dmd/src/phobos" "-Iusr/share/dmd/src/druntime/import" -lib "-odobj/Debug" "-oflibTest.a"...
You can btw disable graying out code parts.