Re: GOBO 3.5 and VE 5.0b (2508) precompiling libraries
Lothar Hansche <lohan-3d/[email protected]> Mon, 23 Jul 2007 22:57:07 +0200
| Newsgroups | gmane.comp.lang.eiffel.gobo.general |
|---|---|
| Message-ID | <[email protected]> |
Hello Eric,
many thanks for you fast anwer.
Eric Bezault schrieb:
> Lothar Hansche wrote:
>
>> Hello,
>>
>> I'm using GOBO 3.5 together with VE 5.0b.
>> Many thanks for the great new package.
>> It works fine without precompiling.
>> And I use geant instead now since a few days for building
>> my executables and documents.
>> Very helpfully are the examples for that.
>> The docu describes not all options an tasks.
>>
>> But last one general question for using:
>> I want precompile whole GOBO and second the GOBO XML directory
>> for instance for VE. Is there a posibility for that?
>> The library.xace in gobo/library does not do this job.
>> (Cannot find class ANY.)
>> I looked in test/precompile, the generated compile_ve.xace file works.
>> But it creates separate clusters in all subdirecties.
>> My own library I want precompile also.
>> But it cannot compile my projekts, because I get the
>> message, that I recompile the Gobo clusters to reflect the
>> changes.
>>
>> Many thanks
>> Lothar Hansche,
>> Berlin, Germany
>>
>
> I don't think it is possible to precompile a library from geant.
> Internally the geant <ve> task uses 'vec -a:' and not 'vec -p:'.
>
I took the notice already beforehand. That wasn't my problem.
I took the exec task:
<exec executable="vec -p:library.xace"/>
> I think you would have to create your precompiled library using
> directly 'vec -p:'.
>
>
Yes, that's right.
But all library.xace files in GOBO have no capability to precompile.
Unfortunately doesn't exist a discription of VE xace files,
only for old format ELD and ESD.
I adapted from several real xace scripts with try and error to understand
the mode of action and wrote than one new XACE file for the whole GOBO
without XML and then for GOBO_XML_CORE separately.
The solution were mounts to several VE Libraries and the element
<option name="include" value="..."/>
And it works fine. XACE, I like it very much.
The listing for GOBO only:
$ cat ${GOBO}/library/precomp_ve.xace
<library name="GOBO">
<description>
description: "Xace file for precompiling Gobo Eiffel Library via VE
5.0b"
library: "Gobo Eiffel Library"
copyright: "Copyright (c) LoHaN 2007, Lothar Hansche, Berlin"
license: "Eiffel Forum License v2 (see forum.txt)"
date: "$Date: 2007/07/21 11:11:00 $"
revision: "$Revision: 3190 $"
</description>
<option name="assertion" value="generate"/>
<option name="debugger" value="true"/>
<cluster name="GOBO" location="${GOBO}/library">
<mount location="${VE_Lib}/kernel/library.xace"/>
<mount location="${VE_Lib}/misc/pool/library.xace"/>
<!--mount location="${VE_Lib}/tool/gargs/library.xace"/-->
<mount location="${VE_Lib}/timedate/library.xace"/>
<!-- kernel -->
<option name="include" value="kernel/basic/**/*.e"/>
<option name="include" value="kernel/elks/**/*.e"/>
<option name="include" value="kernel/io/*.e"/>
<option name="include" value="kernel/misc/*.e"/>
<option name="include" value="kernel/unicode/*.e"/>
<option name="include" value="kernel/support/*.e"/>
<option name="include" value="kernel/spec/ve/*.e"/>
<!-- utility -->
<option name="include" value="utility/**/*.e"/>
<!-- pattern -->
<option name="include" value="pattern/**/*.e"/>
<!-- string -->
<option name="include" value="string/**/*.e"/>
<!-- argument -->
<option name="include" value="argument/**/*.e"/>
<!-- structure -->
<option name="include" value="structure/**/*.e"/>
<!-- time -->
<option name="include" value="time/**/*.e"/>
<!-- lexical -->
<option name="include" value="lexical/**/*.e"/>
<!-- math -->
<option name="include" value="math/**/*.e"/>
<!-- parse -->
<option name="include" value="parse/**/*.e"/>
<!-- regexp -->
<option name="include" value="regexp/**/*.e"/>
</cluster>
</library>
--
No more clusters were generated in the cluster subdirectories.
That was it, what I wanted.
Unfortunately it gives no significant shorter compile time for the
big projects (long link time),for the little projects about 10
until 40 %.
It influences intense the first compilation only.
But I need precompiled libraries for generating the short
HTML-documentation of
the classes via ghtml tool from OT primarily.
Or is there another tool to generate the class documentation without
precompiling?
All the best
Lothar Hansche
Berlin, Deutschland
To Post a message, send it to: [email protected]
To Unsubscribe, send a blank message to: [email protected]
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/gobo-eiffel/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/gobo-eiffel/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[email protected]
mailto:[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/