[Setoolkit-developer] Crosscompiling for unified packaging

[Dagobert M. <da...@ba...>]

Hi Alex,

Am 01.04.2007 um 18:11 schrieb Alex Kiernan:
> On 01/04/07, Dagobert Michelsen <da...@ba...> wrote:
>> I added another mailing list
>>   set...@li...
>> We should discuss things on the list to have an archive of stuff we
>> talked about and to let others participate.
>>
>
> Yup - sounds good to me.

I cc:'ed to the list.

>> PS: Autoconf works great. I am rebuilding the packaging process and
>> used autoconf for sparc, sparcv9, i386 and amd64
>>     without problems.
>
> Excellent - it was well worth committing it; your comments managed to
> trigger the idea of how to make it build the "right" version for a
> particular platform - I'll commit it shortly (I seem to have some
> network problems at the moment).

This sounds difficult to me. It must produce the correct version for
the compiling host regardless of the compiler (SS11 or gcc) and it
must be possible to easily overwrite this. I used setting CC to
"/opt/SUNWspro/bin/cc -xarch=generic64" which would certainly collide
with setting made at a different place in configure.

> One thing which did occur is that if we really wanted to the pieces
> are all there to allow a single platform to cross compile everything
> (I haven't done cross compilers for getting on for 10 years...)

This is (at least for SS11 to my knowledge) currently impossible. See
   http://forum.java.sun.com/thread.jspa?threadID=5104192&tstart=75
   http://forum.java.sun.com/thread.jspa? 
threadID=5072312&messageID=9264958
With gcc this should be possible however, but I prefer sticking to SS11)

One more thing: you moved the examples to share/se. I would like to
keep the directory structure of the package in "RICHPse-form" as
it has always been. The share/se-part is hardcoded. Do you see
a possibility of customizing this via configure (maybe datarootdir?)
to build an package with the customary directory structure?
For a package in blastwave-form the current format is ok.

One last thing: do you think anybody is using the SE toolkit apart
as the groundwork necessary to run Orca or fire up zoom.se?
Should we attempt to port/investigate/document how the examples
match to D-scripts?

One really last thing: I would like to convert the documentation
of the langauge in doc/* to an up-to-date metaformat to produce ascii/ 
html/pdf/man/...
As I have never began a new documentation project, do you have any
experiences with, say, DocBook, doxygen or another recommendation?


Best regards

   -- Dagobert