Empty LST files?

Thalamus via Digitalmars-d-learn digitalmars-d-learn at puremagic.com
Sun Jul 31 13:28:54 PDT 2016


On Sunday, 31 July 2016 at 17:01:32 UTC, Seb wrote:
> On Sunday, 31 July 2016 at 16:55:52 UTC, Seb wrote:
>> On Sunday, 31 July 2016 at 16:48:52 UTC, Thalamus wrote:
>>> On Sunday, 31 July 2016 at 16:08:49 UTC, Seb wrote:
>>>> On Sunday, 31 July 2016 at 15:30:46 UTC, Thalamus wrote:
>>>>> [...]
>>>>
>>>> How about setting the source path directly? With a recent 
>>>> enough dmd version this can be done automatically like here:
>>>> https://github.com/dlang/dmd/pull/5990/files
>>>
>>> Thanks Seb. Has this been included in an official version 
>>> release yet? (I'm not sure how to tell. I've only used Git a 
>>> small amount.)
>>>
>>> thanks!
>>
>> Nope it has been added five days ago.
>> You might grab a dmd-nightly build from here 
>> https://dlang.org/download.html
>
> To clarify I am talking about ___FILE_FULL_PATH__, maybe 
> hard-coding the source directory could also work for you?

In the end, I elected to go with a separate solution for test 
EXEs with the project hierarchy echoed as solution folders. 
Although this adds some extra overhead to maintain this echo, 
that can be automated as part of the main solution's build. And 
it seems to me that there are inherent advantages to going this 
route. For instance, were this all still in one solution, I'd 
either have to add additional configurations (32-bit w/ -cov, and 
64-bit w/ -cov), or I'd have to manually add -cov to each project 
whenever I wanted coverage info and later remove it, or I'd have 
to wait for the code coverage files to be created after every 
run. A separate solution allows me to maintain -cov for all 
configurations isolated from my main development mode. So it's 
there when I want it and gone when I don't, seamlessly.

Thanks to everyone for their input!



More information about the Digitalmars-d-learn mailing list