On 10 October 2013 15:33, Jürgen Schmidt <jogischm...@gmail.com> wrote:
> On 10/10/13 3:05 PM, janI wrote:
>> On 10 October 2013 13:56, Jürgen Schmidt <jogischm...@gmail.com> wrote:
>>> Hi Jan,
>>>
>>> as promised I tried to build the l10n40 branch on MacOS. I started with
>>> my normal config settings and included some languages (keyid bg da de
>>> en-US).
>>>
>>> The first error I got was in l10ntools, makedepend was missing which is
>>> built in soltools. This is strange because l10tools has a build
>>> dependency on soltools. Anyway solving this manually I got the next
>>> error in l10ntools.
>> Firstly thanks for taking time to test the branch.
>>
>> makedepend should be (as you write) built in soltools. I assume you
>> used "build --all --genPO" ?
>
> my first attempt was to build simply with "build --all" from instset_native

That does not work at the moment because I am integrating merge.

I have solved the other problem, which I introduced while trying to
get merge to work in helpcontent2.

if you use:
R1530978

that builds l10ntools cleanly on my ubuntu. (build --all --genPO)

sorry for the inconvinience.

>
>>
>>>
>>> The next problem was that lucene was not built and here the build
>>> dependency is missing in l10ntools/prj/build.lst. Solving manually ...
>>
>> I removed lucene, because I could not see it being used in the make
>> files, however I had recently to "restore" the helplinker since its
>> used in helpcontent2, maybe that uses lucene, I have to dig into that.
>
> lucense is used in the help system to generate the index etc. I believe
> it is done partly during build and later during the first start of the
> help. Can't remember the details.

Thanks I did not know that.
>
>>
>>>
>>> Next problem is a missing hash_map header
>>>
>>> In file included from
>>> .../svn/l10n40/main/l10ntools/source/help/HelpLinker.cxx:24:
>>> .../svn/l10n40/main/l10ntools/source/help/HelpCompiler.hxx:28:20: error:
>>> hash_map: No such file or directory
>>> .../l10n40/main/l10ntools/source/help/HelpCompiler.hxx:37:32: error:
>>> boost/shared_ptr.hpp: No such file or directory
>>
>> both hash_map and shared_ptr should be part of boost, I will try to
>> investigate it a bit.
>>
>> Actually I will modify the makefile, not to include helplinker when doing 
>> genPO.
>
> not sure if I understand but independent of using --genPO or not the
> build should work ;-)

totally agree, but right now it is a floating target, since I am
halfway through integrating merge. Once merge is integrated build will
work as usuad.

when you do "build --all --genPO", it extract all texts, makes
template files ready for pootle.

The workflow will be:
1) build --all --genPO
2) commit templates in svn and update template dir in pootle
3) run "update against templates" in pootle
4) translate
5) commit po files to svn
6) build --all --with-lang="1 2 3 ..."

And right now I work on 6).

rgds
jan I.

>
>
>>
>>>
>>>
>>> It seems that some build dependencies are missing ... I will continue
>>> when I have time ...
>>
>> Thanks a bunch. wait until I have changed the makefile.
>>
>>>
>>> Is the branch in sync with trunk or nearly up-to-date?
>>
>> I merged with trunk just after the 4.0.1 release, but of course I have
>> modified several makefiles and solenv/inc, but that should only be
>> used after l10ntools is generated.
>>
>>>
>>> My recommendation is to build from scratch with a clean env to detect
>>> missing dependencies.
>>
>> I do that approx. 1-2 times pr week, but only on ubuntu.
>>
>> I delete all instances of unxlng6.pro, run configure, bootstrap and
>> then build --all --genPO.
>
> I will try it with --genPO next
>
> Juergen
>
>>
>> This is by the way the reason why I can to change configure.in so it
>> supports multiple platforms in one source tree.
>>
>> rgds
>> jan I.
>>
>>>
>>>
>>> Juergen
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to