[Opencxx-users] Re: [opencxx] Porting to MacOs X

[Alexandre T. <kt...@fr...>]

>>>> I replaced the current Gc in the Cvs version with Gc 6.1. It =20
>>>> compiles
>>>> without any problem but Occ itself does not compile at all, I get =20
>>>> tons
>>>> of errors. The Gcc version
>>>> shipped with the Mosx dev package is 3.1. Which version do you use =20
>>>> to
>>>> compile Occ?
>>>
>>> OpenC++ sources does not conform to namespaces scheme mandated by C++
>>> standard
>>> (i.e. that standard library components live in 'std' namespace).
>>> OpenC++
>>> DOES NOT compile with gcc>=3D3.0. It is not difficult to fix and
>>> somebody has already done it, but nobody had enough will to check it
>>> in.
>>> Go to OpenC++ project page at www.sf.net and search the archive of
>>> opencxx-user, the link to the gcc-3.0 compatible version has been
>>> posted
>>> here.
>>
>> I'll try that.
>
> I am very sorry. I checked myself and it is not there (we started
> archiving messages later than I thought). This is what you need:
>
>   http://www.neci.nj.nec.com/homepages/mic/openc++2.5.12-gcc-3.0.3.tgz
>
> The fix was prepared by Michael Buro (mic at research dot nj dot nec
> dot com). Again, sorry for that.
>
>>
>>>  If you can spare some time to merge the changes with HEAD revision
>>> and check it in, the heavens will thank you (and I will join too).
>>
>> No problem but I haven't used CVS for quite a while...
>
> I can help if there are any issues.
>
>>>> Note: to compile Occ, I duplicated "Makefile.FreeBSD" in "src/Unix"
>>>> and
>>>> used "make -f Makefile.Darwin all".
>>>
>>> *PLEASE* work on CVS HEAD.
>>>
>>> 2.5.12/2.5.13 is difficult to maintain because of code duplication in
>>> its
>>> build system. OpenC++ project does not have resources to maintain it.
>>> Moreover, 2.5.12 does not include test harness nor test suite, which
>>> disables reliable development, because you have no means to verify if
>>> your
>>> contribution breaks the current functionality. It is likely that your
>>> otherwise very valuable work will not be useful if you stick to =20
>>> 2.5.12
>>> .
>>
>> Don't worry, I'm working on the latest tree posted on SourceForge :)
>
> Cool.

Grzegorz,

I merged Bruno's work with the current Cvs tree. The namespace problem =20
is gone but I'm facing now another problem relating to dynamic libs: =20
"metaclass.h" includes some "ltdl.h" header file which does not exist =20
on Mosx (well, Darwin actually). Is there a standard way to handle Dlls =20
across multiple Unix variants (Posix?). Moreover, Dlls have a ".dylib" =20
extension on Darwin, not ".so" like on FreeBSD (although Darwin is Bsd =20
based).

Any help is welcome :)

Alex

------------------------------------------------------------------------=20
-
Alexandre Tolmos
E-mail:=A0...@fr...
ICQ: 92964905
------------------------------------------------------------------------=20
-
"Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn."
------------------------------------------------------------------------=20
-