RE: Re: using XS with C++

Thanks. I tried what you suggested. One problem is that the Makefile is still setting CC = cc so it still tries to compile with the C compiler. Here's the output:

judyf: betaman.portsoft.com.138> make
mkdir ./blib
mkdir ./blib/lib
mkdir ./blib/arch
mkdir ./blib/arch/auto
mkdir ./blib/arch/auto/myclass
mkdir ./blib/lib/auto
mkdir ./blib/lib/auto/myclass
mkdir ./blib/man3
cp myclass.pm ./blib/lib/myclass.pm
AutoSplitting ./blib/lib/myclass.pm (./blib/lib/auto/myc
cc -c   -O     -DVERSION=\"0.01\"  -DXS_VERSION=\"0.01\"
perl5/sun4-solaris/5.00405/CORE  myclass.cc
cc: No input file specified, no output generated
*** Error code 1
make: Fatal error: Command failed for target `myclass.o'
[download]

I did an 'ls' and it turns out that myclass.cc does not exist. Neither does myclass.c for that matter. Then, I took out the line:

    'XS'       => {'myclass.xs' => 'myclass.cc'},

in Makefile.PL. Then did a 'make clean' and reran '
perl Makefile.PL',
then 'make'. Here's the output:

<CODE>
judyf: betaman.portsoft.com.138> make
mkdir ./blib
mkdir ./blib/lib
mkdir ./blib/arch
mkdir ./blib/arch/auto
mkdir ./blib/arch/auto/myclass
mkdir ./blib/lib/auto
mkdir ./blib/lib/auto/myclassmkdir ./blib/man3
cp myclass.pm ./blib/lib/myclass.pm
AutoSplitting ./blib/lib/myclass.pm (./blib/lib/auto/myclass)
/bin/perl -I/usr/local/lib/perl5/sun4-solaris/5.00405 -I/usr/local/lib
+/perl5 /us
r/local/lib/perl5/ExtUtils/xsubpp  -C++ -typemap /usr/local/lib/perl5/
+ExtUtils/t
ypemap -typemap typemap myclass.xs >myclass.tc && mv myclass.tc myclas
+s.c
Please specify prototyping behavior for myclass.xs (see perlxs manual)
cc -c   -O     -DVERSION=\"0.01\"  -DXS_VERSION=\"0.01\" -Kpic -I/usr/
+local/lib/
perl5/sun4-solaris/5.00405/CORE  myclass.c
"/home/judyf/perlwork/myclass/myclass.h", line 9: undefined
 or not a type: class

... (and so on with rest of errors)
[download]

Not sure why it's missing these lines in Makefile when it's in C++ mode. Also, I edited Makefile and these lines are still set to: <CODE> CC = cc LD = cc <CODE> I'll keep looking into it but if you have any further suggestions, I'm all ears. Thanks.

Comment on RE: Re: using XS with C++ Select or Download Code

Replies are listed 'Best First'.
RE: RE: Re: using XS with C++ by tye (Sage) on Jul 22, 2000 at 07:43 UTC
I'm pretty sure that the `XSOPT=>'-C++'` option is only partially implemented. It only does (at most) one of something like 3 things that it should do. Now, I think the direction C and C++ compilers have moved is that you use "cc" to compile both C and C++ files and the compiler determines what type of code it is compiling by whether the file name ends in .c or one of .cc, .cpp, .c++, .cxx, etc., where each compiler recognizes about two different extensions for C++ code. So the `CC=cc` is probably not a problem. The problem is that it is generating a file named myclass.c instead of myclass.cxx. I managed to use C++ in XS as part of some other strange work I was doing (see the latest versions of Win32API::File, for example). I used .cxx and wrote my own rules out with `sub MY::postamble`. At least the latest MakeMaker knows how to compile a .cxx file if you ask it to.	[reply] [d/l] [select]

Replies are listed 'Best First'.

RE: RE: Re: using XS with C++
by tye (Sage) on Jul 22, 2000 at 07:43 UTC

I'm pretty sure that the XSOPT=>'-C++' option is only partially implemented. It only does (at most) one of something like 3 things that it should do.

Now, I think the direction C and C++ compilers have moved is that you use "cc" to compile both C and C++ files and the compiler determines what type of code it is compiling by whether the file name ends in .c or one of .cc, .cpp, .c++, .cxx, etc., where each compiler recognizes about two different extensions for C++ code. So the CC=cc is probably not a problem. The problem is that it is generating a file named myclass.c instead of myclass.cxx.

I managed to use C++ in XS as part of some other strange work I was doing (see the latest versions of Win32API::File, for example). I used .cxx and wrote my own rules out with sub MY::postamble. At least the latest MakeMaker knows how to compile a .cxx file if you ask it to.

[reply]
[d/l]
[select]