You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@googlemail.com> on 2012/01/05 12:06:32 UTC
Localized builds
Hi,
maybe i have missed somehting but i stumbled over a problem to build
localized packages.
I used configure with --with-lang="en-US de" and got a problem in
instsetoo_native to resolve a dependency to module l10n
The solution is to put a source.config file besides main
.../main
.../extras
.../source.config
source.config
###
[repositories]
main=active
extras=active
###
My question is how do others make localized builds without this file?
Any ideas?
Juergen
Re: Localized builds
Posted by Michael Stahl <ms...@openoffice.org>.
On 05/01/12 12:06, Jürgen Schmidt wrote:
> I used configure with --with-lang="en-US de" and got a problem in
> instsetoo_native to resolve a dependency to module l10n
>
> The solution is to put a source.config file besides main
> My question is how do others make localized builds without this file?
i'm guessing they don't.
> Any ideas?
for inspiration, my ideas on getting rid of the source_config horror:
http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201109.mbox/%3Cj48gg5$ksu$1@dough.gmane.org%3E
regards,
michael
Re: Localized builds
Posted by Andre Fischer <af...@a-w-f.de>.
I made some changes for issue 118778
(https://issues.apache.org/ooo/show_bug.cgi?id=118778) so that when the
--with-lang option is given to configure the extras/ directory is added
automatically to the list of repositories.
See the issue comments for more details.
Regards,
Andre
On 05.01.2012 19:41, Andrew Rist wrote:
>
>
> On 1/5/2012 3:06 AM, Jürgen Schmidt wrote:
>> Hi,
>>
>> maybe i have missed somehting but i stumbled over a problem to build
>> localized packages.
>>
>> I used configure with --with-lang="en-US de" and got a problem in
>> instsetoo_native to resolve a dependency to module l10n
>>
>> The solution is to put a source.config file besides main
>>
>> .../main
>> .../extras
>> .../source.config
>>
>> source.config
>> ###
>> [repositories]
>> main=active
>> extras=active
>> ###
>>
>> My question is how do others make localized builds without this file?
> I am running into this same problem - with one caveat...
> the file seems to need to be *source_config *(with an underscore as
> opposed to a '.')
>
> Is there a downside to checking this in? This will block doing a
> --with-lang build on the buildbot if this is not in svn.
>
> A.
>>
>> Any ideas?
>>
>> Juergen
>
>
Re: Localized builds
Posted by Andrew Rist <an...@oracle.com>.
On 1/5/2012 3:06 AM, Jürgen Schmidt wrote:
> Hi,
>
> maybe i have missed somehting but i stumbled over a problem to build
> localized packages.
>
> I used configure with --with-lang="en-US de" and got a problem in
> instsetoo_native to resolve a dependency to module l10n
>
> The solution is to put a source.config file besides main
>
> .../main
> .../extras
> .../source.config
>
> source.config
> ###
> [repositories]
> main=active
> extras=active
> ###
>
> My question is how do others make localized builds without this file?
I am running into this same problem - with one caveat...
the file seems to need to be *source_config *(with an underscore as
opposed to a '.')
Is there a downside to checking this in? This will block doing a
--with-lang build on the buildbot if this is not in svn.
A.
>
> Any ideas?
>
> Juergen
Re: Localized builds
Posted by Oliver-Rainer Wittmann <or...@googlemail.com>.
Hi,
On 06.01.2012 11:33, Jürgen Schmidt wrote:
> On 1/5/12 8:24 PM, Ariel Constenla-Haile wrote:
>> Hi Jürgen,
>>
>> On Thu, Jan 05, 2012 at 12:06:32PM +0100, Jürgen Schmidt wrote:
>>> Hi,
>>>
>>> maybe i have missed somehting but i stumbled over a problem to build
>>> localized packages.
>>>
>>> I used configure with --with-lang="en-US de" and got a problem in
>>
>> en-US is the default, always built, so it is not needed to explicitly in
>> the switch.
>>
>>> instsetoo_native to resolve a dependency to module l10n
>>>
>>> The solution is to put a source.config file besides main
>>>
>>> .../main
>>> .../extras
>>> .../source.config
>>
>> it's source_config
>>
>>> source.config
>>> ###
>>> [repositories]
>>> main=active
>>> extras=active
>>> ###
>>>
>>> My question is how do others make localized builds without this file?
>>
>> no, this is -AFAIK- the only way it's done.
>> See http://s.apache.org/fAe
>> and the references quoted here:
>> http://openoffice.org/projects/www/lists/dev/archive/2011-06/message/40
>>
>> IMO a terrible idea, because supposing you checked out the trunk:
>>
>> trunk
>> |--- main/
>> |--- extras/
>> |--- ext_sources/
>> |--- source_config<--- needed by localized builds
>> |--- logs/<--- written by build.pl if --enable-verbose
>>
>>
>> you are putting stuff that is not supposed to be committed.
>> Of course it can be added to the ignored list.
>
> mmh, ok it seems this needs some more cleanup work
>
> but i don't understand your point why it is a bad idea to create this file
> besides main, extras.
>
> We have 2 choices
> 1. create this file and check it in for now. Do some deeper analysis to get rid
> of it later
>
> 2. we generate this file during the bootstrap and do the same analysis and
> remove it later
>
> I would prefer 2.
>
> Any ideas?
>
+1 for option 2
Best Regards, Oliver.
Re: Localized builds
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 1/5/12 8:24 PM, Ariel Constenla-Haile wrote:
> Hi Jürgen,
>
> On Thu, Jan 05, 2012 at 12:06:32PM +0100, Jürgen Schmidt wrote:
>> Hi,
>>
>> maybe i have missed somehting but i stumbled over a problem to build
>> localized packages.
>>
>> I used configure with --with-lang="en-US de" and got a problem in
>
> en-US is the default, always built, so it is not needed to explicitly in
> the switch.
>
>> instsetoo_native to resolve a dependency to module l10n
>>
>> The solution is to put a source.config file besides main
>>
>> .../main
>> .../extras
>> .../source.config
>
> it's source_config
>
>> source.config
>> ###
>> [repositories]
>> main=active
>> extras=active
>> ###
>>
>> My question is how do others make localized builds without this file?
>
> no, this is -AFAIK- the only way it's done.
> See http://s.apache.org/fAe
> and the references quoted here:
> http://openoffice.org/projects/www/lists/dev/archive/2011-06/message/40
>
> IMO a terrible idea, because supposing you checked out the trunk:
>
> trunk
> |--- main/
> |--- extras/
> |--- ext_sources/
> |--- source_config<--- needed by localized builds
> |--- logs/<--- written by build.pl if --enable-verbose
>
>
> you are putting stuff that is not supposed to be committed.
> Of course it can be added to the ignored list.
mmh, ok it seems this needs some more cleanup work
but i don't understand your point why it is a bad idea to create this
file besides main, extras.
We have 2 choices
1. create this file and check it in for now. Do some deeper analysis to
get rid of it later
2. we generate this file during the bootstrap and do the same analysis
and remove it later
I would prefer 2.
Any ideas?
Juergen
Re: Localized builds
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Jürgen,
On Thu, Jan 05, 2012 at 12:06:32PM +0100, Jürgen Schmidt wrote:
> Hi,
>
> maybe i have missed somehting but i stumbled over a problem to build
> localized packages.
>
> I used configure with --with-lang="en-US de" and got a problem in
en-US is the default, always built, so it is not needed to explicitly in
the switch.
> instsetoo_native to resolve a dependency to module l10n
>
> The solution is to put a source.config file besides main
>
> .../main
> .../extras
> .../source.config
it's source_config
> source.config
> ###
> [repositories]
> main=active
> extras=active
> ###
>
> My question is how do others make localized builds without this file?
no, this is -AFAIK- the only way it's done.
See http://s.apache.org/fAe
and the references quoted here:
http://openoffice.org/projects/www/lists/dev/archive/2011-06/message/40
IMO a terrible idea, because supposing you checked out the trunk:
trunk
|--- main/
|--- extras/
|--- ext_sources/
|--- source_config <--- needed by localized builds
|--- logs/ <--- written by build.pl if --enable-verbose
you are putting stuff that is not supposed to be committed.
Of course it can be added to the ignored list.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina