On 2006-10-09 12:09+0200 Werner Smekal wrote:

> Hi,
>
> I managed to make plplot compile with the Open Watcom compiler
> (http://www.openwatcom.org) and was also able to run x01c with the
> wingcc driver.

This takes me back a long way.  I did a lot of my programme development as a
graduate student (in the 70's) using the WATFOR (Waterloo Fortran) compiler.
That compiler was probably one of the better fortran compilers available at
that time for IBM equipment. If you read the openwatcom history, WATFOR was
the first step in the openwatcom effort.

It sounds like after a semi-open beginning they closed the compiler
development effort for a long time, but now they are beginning to reopen it
again.  However, in my opinion, they are too tentative about this. The lack
of Linux platform is a problem for this compiler.  According to
http://www.openwatcom.org/index.php/Win32ver_on_Linux openwatcom partially
works under wine/linux, but that is insufficient.

> There were some problems though:
>
> 1) wmake, the watcom make, doesn't like '+' in filenames - therefore it
> doesn't compile the c++ bindings. The most simple solution would be to
> just rename the c++-bindings directory to cxx and make appropriate
> changes everywhere. The only drawback would be (at least I think so),
> that we loose the 'history' of these files in cvs, since cvs can't
> rename files. What do you think about that?

Since openwatcom.org is an open-source project, I think your best bet is to
make a bug report there to insure they support valid directory/filenames.
The alternative of changing bindings/c++ AND examples/c++ to the cxx form
means quite a few changes to not only our CBS, but also our ABS.  This is in
addition to the issue you pointed out of losing all the history for all
files in the two c++ directories.

>
> 2) watcom knows isnan, but CBS doesn't find it, since isnan is defined
> in math.h. So check_function_exists(isnan HAVE_ISNAN) doesn't work, we
> would need a similar solution like for TestBrokenIsnanCXX.cxx. Should I
> do the changes or is there a possibility for check_function_exists to
> add a header before (cmake documentation doesn't say so).

I am not sure.  I think you are going to have to experiment with
check_function_exists (paying close attention to its log-file results) to
find out.  If that continues to not give what you need, then the alternative
of writing a special check is fine as well.

>
> 3) There is also problem with the export of plsc, which clashes with
> changes Arjen did, but we try to figure this out.
>
> Apart from that it seems, that also Open Watcom is now supported (thanks
> to CBS). And Open Watcom has also a fortran compiler - but this needs
> still to be tested.

Good work.  I will also be most interested to see how well it does for our
two fortran (f77 and f95) interfaces.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to