Am 24.09.2015 um 23:55 schrieb Benjamin Chambers:
> On 9/24/2015 1:44 PM, clipka wrote:
>> As far as this is concerned, while testing with VS2010 I just noticed
>> that the description ("Creating toFloat.h..." or whatever) isn't
>> actually printed to the build output even if the custom build step
>> obviously runs (as demonstrated by toFloat.h reappearing after having
>> been deleted).
>> A hint that the custom build step was run seems to be a log file
>> generated in "build\toFloat\x64\Release" (in case of building for x64),
>> named "toFloat.write.1.tlog".
>> If you can't get the Custom Build Step mechanism to do the job, you
>> might want to try the Post-Build Event mechanism instead, though IIRC
>> there was /something/ undesirable about it.
> I've tried both, actually, and neither one indicates in the log file
> that the step was run, nor do they generate the header file.
That's certainly strange. It does build the .exe that's supposed to
generate them, right?
Post a reply to this message