[ODE] documentation initiative

[Shaul Kedem]

Russ,
 As far as I know there is no way in hell we could use
different compilers than the one the end user uses
(for example, using cross-platform gcc with intel's
compiler, or even msvc 7.0 will end up badly),
moreover, if the time will come for a C++ wrapper it
will be practically impossible to map between how one
compiler does its name mangling with the other.

 I suggest droping this and simply building a better
method of operation, for example, if everybody are so
keen on dlls, give them a stand alone project which
creates the dll from a batch file (nmake and cl can be
ran from an msvc makefile, without the need for a
project), not to say gl hasn't done a great job (you
might recall I've been up a couple of nights to check
his project as well).


oh- and check cmake.org, it's a cross platfrom
makefile (and msvc projects) creator, free and open.

 3 bits from me (.5 a bit is impossible, i think)

Shaul

--- Russ Smith <russ at q12.org> wrote:
> 
> people,
> 
> ODE would certainly benefit from having pre-built
> libraries for various
> platforms. however, there are a few practical
> problems.
> 
> (1) for windows, there are a number of different
> compilers that people
> use. VC6, .net, borland, intel, and at least two
> flavors of gcc. do we
> need pre-built libraries for all of them? ODE has a
> C interface, so if
> the C ABI is *identical* between these compilers
> then one compiler would
> be enough. in that case it would have to be the
> fastest/best compiler,
> otherwise people will want to compile their own
> anyway. intel compilers
> claim to be better than gcc, so maybe intel is a
> good choice (i have
> never used it). gcc is not a strong optimizing
> compiler on windows/x86,
> at least compared to other windows compilers.
> 
>         --> can someone tell me if the C ABI is
> identical for all
>             windows compilers (or can be made so
> with compiler flags).
>             if not, what are the differences?
> 
> (2) an automatic build system is a must - nobody
> wants to run through 20
> compile cycles by hand every time something in CVS
> changes (remember
> that we have debug/release options, float/double
> options, so we must
> build for all option settings for all platforms). on
> sourceforge it is
> (i think) possible to run automatic builds for *nix
> environments, but
> not for windows. how can we auto-build windows libs
> without a dedicated
> windows machine? one answer is to build
> cross-platform using gcc on
> linux. but this wont please every windows user, see
> (1).
> 
> of course this would take time to set up, but it
> might be worth it
> provided the above two problems can be solved.
> 
> russ.
> 
> -- 
> Russell Smith
> http://www.q12.org
> _______________________________________________
> ODE mailing list
> ODE at q12.org
> http://q12.org/mailman/listinfo/ode


__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html