[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: KDE/kdetoys/kweather
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2006-02-22 9:30:38
Message-ID: 200602221029.26429.nicolasg () snafu ! de
[Download RAW message or body]

>List:       kde-commits
>Subject:    Re: KDE/kdetoys/kweather
> From:       Nadeem Hasan <nhasan () nadmm ! com>
>Date:       2006-02-22 3:24:32
>Message-ID: 200602212224.37366.nhasan () nadmm ! com
(...)

>On Tuesday 21 February 2006 20:30, Script Kiddy wrote:
>> SVN commit 512175 by scripty:
>>
>> Simplify the "messages" target
>>  messages: rc.cpp
>> -     $(EXTRACTRC) *.ui > rc.cpp
>> -     $(XGETTEXT) rc.cpp *.cpp *.h -o $(podir)/kweather.pot
>> -     rm -f rc.cpp
>> +     $(XGETTEXT) *.cpp *.h -o $(podir)/kweather.pot
>
>How is the .ui file handled? Is the message target supposed to be built after 
>uic has been run (i.e. after building the source)?

The script calling the "messages" target (or calling the brand new Messages.sh 
script) has already run $(EXTRACTRC) on .ui .rc and .kcfg files in the same 
directory than the Makefile.am file (or than the Messages.sh file).

(If you are interested, the script directly calling this is
branche/work/kde4-l10n/scripts/extract-messages.sh
(which was formerly the extract-messages in admin/cvs.sh))

Repeating this step makes that the messages are again added to the rc.cpp, 
creating extra source references.

As for building the source, Scripty does not build the source at all.

Have a nice day!

[prev in list] [next in list] [prev in thread] [next in thread]