Closed ghost closed 5 years ago
Oh. From the current release and onwards, I am using LDC to build binaries on all platforms, so I removed a workaround for this problem...
I don't know how this happens. The workaround is simply to put the build command twice. For some reason the second time around it builds fine.
The undefined reference refers to a module that is dynamically generated in a preGenerateCommand
, that's the only clue I have about why this happens.
I'll put back the workaround when I get back on my machine for now.
That's because of the command. The project properties (e.g what's interesting here is the list of source in this case) are already defined when the description is loaded i think. I'm almost sure i've heard before of a similar issue encountered by someone else.
solution would be to generate locally by hand and include the auto generated file in your repo then.
we do that for DCD too (constant completions for traits), the module is regenerated by hand.
I looked up what other people might be doing for that, and saw this: git update-index --assume-unchanged
. With this I can add an empty file to the repo, and its changes should be ignored at all time.
Apparently it's fixed my Travis build with dmd-beta
, so it seems to be working
Actually git still nags me about the changes when the file is filled... But I'll see about that later.
Yes, i can confirm it's good now, just relaunched a buildkite job and it's green. Thanks.
When it's tested with DMD ~master (buildkite) we got this log:
(linking error due to undefined reference)