Re: [SOSlib-devel] AIX built + dynamic compilation using gcc + help required

[Christoph F. <xt...@tb...>]

hi andrew,

 > I have managed get SOSlib to build on AIX and
 > more importantly I have managed to implement dynamic compilation using
 > g++ and shared libraries the same way as I did for windows using tcc.
 > The performance seems to be in the same ball park as the compiled code
 > was achieving on windows.  I assumed that tcc is i386 specific.

that's great news!

 > I'm effectively working on my own branch as I have not resolved the
 > `bug` in the most recent checked in source that's caused our model to
 > fail.  So I'll probably just email you the relevant source files.  I'll
 > try to document all the hacks required to get SOSlib to build
 > on AIX.

yes, please do so

 > One issue:
 > 
 > I need to get hold of the include directory for sundials and SOSlib for
 > the dynamic compilation, that is in the code and not in a build file.
 > All the files use temporary filenames
 > 
 > Is there a way to have something like:
 > 
 > #define SUNDIALS_INSTALLATION "/usr/local/"
 > #define SOSLIB_INSTALLATION "/usr/home/finney"
 > 
 > or
 > 
 > #define SUNDIALS_INCLUDE "/usr/local/include"
 > #define SOSLIB_INCLUDE "/usr/home/finney/include"
 > 
 > inserted into config.h
 > 
 > ?
 > 
 > I assume this means some kind of configure.in hack
 > I'm not exactly a guru on that so guidance would be nice.

yes that's correct. the easiest way would be to hand the required
information via command line options to the configure script into the
building process so that it automatically ends up in the config.h. are
the includes above all you need? i can write you a small m4 macro file
tonight that handles the commandline solution if you like.

 > 
 > Background:
 > 
 > At the moment I have to hard code the include path which is not ideal.
 > I tried using the same technique as windows: locate the sos
 > shared/dynamic library and then locate the include directory relative to
 > that.  I ran into a showstopper on that on AIX : missing struct
 > definition in the include files.  Anyway that's not the ideal approach
 > using the above would be better in an open-source build to install
 > environment.

i totally agree!

=;) xtof