Fw: [wxPython] Problem building 2.2.2 on Solaris...
This is from a wxPython user. Any advice?
Greetings...
Using SunOS 5.7, Python 1.5.2, Distutils 1.0.1, wxGTK 2.2.2 I'm using WorkShop Compilers 5.0 98/12/15 C 5.0 which I have used to build everything else.
Everything is fine other than the build insists in compiling with cc. Since .cpp files are being compiled, cc objects. It should be compiling with the C++ compiler (/opt/SUNWspro/bin/CC in this case) instead. It works fine if I cut and paste the compile commands and substitute the CC.
Anyone know how do I tell distutils to use the C++ compiler? I don't really know anything about distutils...
-- Robin Dunn Software Craftsman robin@AllDunn.com http://wxPython.org Java give you jitters? http://wxPROs.com Relax with wxPython!
on Nov 3, 2000, 09:44, Robin Dunn std::cout'ed: | This is from a wxPython user. Any advice? Yes -- hack distutils. That is what I had to do. Everything worked fine (although linker had to be re-run (wxPython might need a C++ linker)). As a side-comment, is there any simple way to specify a _particular_ compiler/linker for a build in distutils? Something along the lines of CXX = g++ in the traditional makefile context. ivr -- VB, by comparison, treats you like a secretary pecking on MS Office. -- Phlip, on c.l.c++
As a side-comment, is there any simple way to specify a _particular_ compiler/linker for a build in distutils? Something along the lines of
CXX = g++ Currently not supported. Here is the source code snippet from build_ext.py: # XXX and if we support CFLAGS, why not CC (compiler # executable), CPPFLAGS (pre-processor options), and LDFLAGS # (linker options) too?
Workarounds: make an alias or a link from cc to gcc Bastian
participants (3)
-
Bastian Kleineidam -
Igor V. Rafienko -
Robin Dunn