Ok, thanks :)
I think that would help
-Sneha
Rob Hamflett wrote:
>
> Yeah. I just use a response file because I have a fair few preprocessor
> defines. You can certainly
> just list them individually on the command line.
>
> Rob
>
> Sneha Gharpure wrote:
>> Hi,
>>
>> Thanks for the reply
Yeah. I just use a response file because I have a fair few preprocessor
defines. You can certainly
just list them individually on the command line.
Rob
Sneha Gharpure wrote:
> Hi,
>
> Thanks for the reply.
>
> What I understood from your reply is that say English.txt will have list of
> all
Hi,
Thanks for the reply.
What I understood from your reply is that say English.txt will have list of
all the preprocessor variables say $(var.LicenseFile). And these variables
are given at the time of compilation to candle. So rather than using a
text file, can it be done by supplying is as a
For the parts that can't be localised, I use preprocessor variables. All the
English specific stuff
is defined in English.txt and the Japanese stuff is defined in Japanese.txt.
In my Makefile I have
separate command lines for the English and Japanese builds, which take
parameters of @English
Hi,
The scenario is that the name of the license agreement file is to be
localized. The source file for the license agreement is specified as
follows.
This gives an error error LGHT0100 : File of type 'File' with name
'$(loc.LicenseFile)' could not be found.
Is there any way to localiz
5 matches
Mail list logo