Roman Yakovenko wrote:
On Tue, Dec 2, 2008 at 3:15 PM, Marcus Lindblom <[EMAIL PROTECTED]> wrote:
Ok. It came right back at me:
pyopensg/src> ** the above **
Could not determine compiler setting.
Could not determine GCCXML_FLAGS setting.
pyopensg/src>
So, I changed it to run my compiled gccxml (pretty recent cvs head) and
added "--gccxml-compiler cl" (I use VS9 and python 2.6) and fixed the
include paths (pyopensg retrieves includepaths from the osg2-config python
script, which used /I instead of /I and also had some non-escaped
backslashes (turing 'c:\program files\boost' into 'c:\program files oost' as
can be seen above :)
Running the modified cmd-line made gccxml run and print a whole lot,
starting with:
j:/3rd/OpenSG/opensg2_trunk/build.win32.cl.9.0/instlinks/include/OpenSG/OSGConfig.h:135:2:
error: #error Endian determination : could not guess your plattform
and ending up with an ICE.
It seems as I have to add a few defines and such to get the opensg-sources
to identify the compiler correctly.
I can handle the osg2-config script myself, and probably figure out what
defines are necessary, but where do I set compiler-arg + defines that are
used when doing the cache-step that calls the above command?
gen_bindings.py file contains the following lines:
813 mb = ModuleBuilder([main_header_filename],
814 working_directory = ".",
815 include_paths=inc_path,
816 cache=cache_file+".module",
817 define_symbols=defines,
818 ignore_gccxml_output=True,
819 optimize_queries=use_query_opt,
820 #start_with_declarations=["OSG",],
821 cflags=opensg_cflags + " " + boost_cflags)
opensg_cflags, boost_cflags variables contains the configuration flags
Yes, but IIUC, this is way after the call to gccxml that I ran above,
since the follwing is printed after the 'INFO gccxml cmd: ...' in the
log-file in my first post:
566 print "Auto-building list of node cores using .fcd files... "
Is this cache stuff in PyOpenSG or Py++? (because I can't seem to find any
such call in gen_bindings.main() nor nearby related modules, unless I've
missed something).
I don't understand the question, sorry :-(
No worries. :)
The call to gccxml that you asked me to run does not produce a valid
ouput file, because it's needs fixing.
So, I'm guessing a bit here, but since the log contains stuff about
cache file load failure and cache creation, which does the gccxml-call
that I need to augment with defines and --gccxml-compiler option, I
assumed I need to fix the gccxml call in the cache-creation thingy, not
the call to ModuleBuilder way below. (which tries to use the empty file
that gccxml failed to create earlier.)
So, my question is, where does that gccxml call come from, and how do I
change it's parameters? (Is even a py++ thing, or does it come from a
pyopensg somewhere I've missed?)
(I don't think the gccxml-call happens because of the call to the
ModuleBuilder at line 813, although I might be wrong?)
Does that make sense?
I'll tinker with the ModuleBuilder a bit anyway.. to see if it helps,
but the order of output makes me think the problem is somewhere else.
Cheers,
/Marcus
P.S. Thanks for helping out! I'm ping-pong:ing a bit between the
opensg-list and this one, so if I need to address my questions the other
way, let me know.
_______________________________________________
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://mail.python.org/mailman/listinfo/cplusplus-sig
