Re: [Cs-dev] Not compiling
Date | 2012-04-27 18:00 |
From | Tito Latini |
Subject | Re: [Cs-dev] Not compiling |
Attachments | None |
Date | 2012-04-27 18:05 |
From | Victor Lazzarini |
Subject | Re: [Cs-dev] Not compiling |
Attachments | None None |
looks like swig has not regenerated the python interface file after changes in the api Victor Lazzarini john ffitch <jpff@codemist.co.uk> wrote: git pull followed by make.... [ 86%] Building CXX object interfaces/CMakeFiles/_csnd.dir/python_interfacePYTHON_wrap.cxx.o cd /home/jpff/Sourceforge/csound/New/csound6/interfaces && /usr/bin/c++ -D_csnd_EXPORTS -DUSE_DOUBLE -D_CSOUND_RELEASE_ -DCS_DEFAULT_PLUGINDIR=\"/usr/local/lib/csound/plugins64-6.0\" -DUSE_LRINT -DLINUX -g -fPIC -I/usr/local/include -I/home/jpff/Sourceforge/csound/New/csound6/./H -I/home/jpff/Sourceforge/csound/New/csound6/./Engine -I/home/jpff/Sourceforge/csound/New/csound6/. -I/home/jpff/Sourceforge/csound/New/csound6 -I/home/jpff/Sourceforge/csound/New/csound6/interfaces -I/usr/include/python2.7 -I/usr/lib64/jvm/java/include -I/usr/lib64/jvm/java/include/linux -fvisibility=hidden -Wno-format -g -o CMakeFiles/_csnd.dir/python_interfacePYTHON_wrap.cxx.o -c /home/jpff/Sourceforge/csound/New/csound6/interfaces/python_interfacePYTHON_wrap.cxx /home/jpff/Sourceforge/csound/New/csound6/interfaces/python_interfacePYTHON_wrap.cxx: In function ���PyObject* _wrap_csoundPreCompile(PyObject*, PyObject*)���: /home/jpff/Sourceforge/csound/New/csound6/interfaces/python_interfacePYTHON_wrap.cxx:9843:38: error: ���csoundPreCompile��� was not declared in this scope /home/jpff/Sourceforge/csound/New/csound6/interfaces/python_interfacePYTHON_wrap.cxx: In function ���PyObject* _wrap_Csound_PreCompile(PyObject*, PyObject*)���: /home/jpff/Sourceforge/csound/New/csound6/interfaces/python_interfacePYTHON_wrap.cxx:18232:25: error: ���class Csound��� has no member named ���PreCompile��� make[2]: *** [interfaces/CMakeFiles/_csnd.dir/python_interfacePYTHON_wrap.cxx.o] Error 1 make[2]: Leaving directory `/home/jpff/Sourceforge/csound/New/csound6' make[1]: *** [interfaces/CMakeFiles/_csnd.dir/all] Error 2 make[1]: Leaving directory `/home/jpff/Sourceforge/csound/New/csound6' make: *** [all] Error 2 ==John ffitch ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/csound-devel |
Date | 2012-04-27 18:46 |
From | jpff@cs.bath.ac.uk |
Subject | Re: [Cs-dev] Not compiling |
The whole point of makefiles is to regenerate files whose sources change. It is the responsibility of cmake to rebuilt such things. Actually as I do not use any python I am happy if it never created it, but the current state is another failing of the cmake build system from my point of view. > Yes, perhaps John called `cmake .' in csound6 dir > and csound6/interfaces contains the old python_interfacePYTHON_wrap.cxx > > With a separate build dir is better. > A separate build directory is a TOTAL PITA. Slows down work by nearly a factor of 2, takes too much screen space, fails gdb, fails etags..... This system worked until today. So either the new code is bust or the build system is ==John ff > On Fri, Apr 27, 2012 at 06:05:40PM +0100, Victor Lazzarini wrote: >> looks like swig has not regenerated the python interface file after >> changes in the api >> >> >> Victor Lazzarini >> >> john ffitch |
Date | 2012-04-27 18:58 |
From | Steven Yi |
Subject | Re: [Cs-dev] Not compiling |
But it looks like this python_interfacePYTHON_wrap.cxx was generated in the csound6/interfaces folder, not where the cmake build folder is. Did you run SCons with this csound6 folder before? In normal Cmake usage, and with the current design of the cmake build files to generate files into the build folder, this situation should not ever occur, and must be due to something outside of the Cmake build. So I do not think it is either the code, or the build system, but a third situation. On Fri, Apr 27, 2012 at 6:46 PM, |
Date | 2012-04-27 19:00 |
From | Steven Yi |
Subject | Re: [Cs-dev] Not compiling |
And however.... I just pulled from Git and tried a build and got a similar error to John, for both the python and java interfaces here. So perhaps I read John's error message incorrectly. I have dinner cooking now, but will look at the root cause here in a moment. On Fri, Apr 27, 2012 at 6:58 PM, Steven Yi |
Date | 2012-04-27 19:03 |
From | Felipe Sateler |
Subject | Re: [Cs-dev] Not compiling |
On Fri, Apr 27, 2012 at 14:46, |
Date | 2012-04-27 19:10 |
From | Steven Yi |
Subject | Re: [Cs-dev] Not compiling |
No, I've just taken a look and I think it is a failure in the build. It probably wasn't noticed as the headers that the .i files include had not been changing up until now. I will look at modifying the CMake files to add that they are generated, or to always generate (the Scons build did this I believe). On Fri, Apr 27, 2012 at 7:03 PM, Felipe Sateler |
Date | 2012-04-27 19:12 |
From | jpff@cs.bath.ac.uk |
Subject | Re: [Cs-dev] Not compiling |
I delete the python_interfacePYTHON_wrap.cxx file and run make again. Same error, and no as far as i can remember i have not run scons on this machine/directory > But it looks like this python_interfacePYTHON_wrap.cxx was generated > in the csound6/interfaces folder, not where the cmake build folder is. > Did you run SCons with this csound6 folder before? In normal Cmake > usage, and with the current design of the cmake build files to > generate files into the build folder, this situation should not ever > occur, and must be due to something outside of the Cmake build. So I > do not think it is either the code, or the build system, but a third > situation. > > > > On Fri, Apr 27, 2012 at 6:46 PM, |
Date | 2012-04-27 19:23 |
From | Steven Yi |
Subject | Re: [Cs-dev] Not compiling |
I was able to delete the python wrap I had here and it built correctly. I'm looking at the SWIG options for extra dependencies for Cmake now. Currently cmake is tracking only changes in the .i file, but not anything beyond that. I'm going to add .h files that are real dependencies. This should improve tracking of dependencies and actually get us to a better place than which we had with Scons, which was regenerating and compiling the interfaces every time. Could you try making a modification to the .i file in csound6/interfaces and then rerunning cmake? That should force a regeneration for now until I can have this done properly. Thanks! steven On Fri, Apr 27, 2012 at 7:12 PM, |
Date | 2012-04-27 19:48 |
From | Steven Yi |
Subject | Re: [Cs-dev] Not compiling |
I've committed the change. Changes look like: + set(SWIG_MODULE_csnd_EXTRA_DEPS ../H/csound.h ../H/cfgvar.h ../H/csound.hpp + cs_glue.hpp csPerfThread.hpp CsoundFile.hpp + CppSound.hpp filebuilding.h Soundfile.hpp) to the interfaces/CMakeLists.txt. I add the included headers I saw in the .i file for python, then copied those to the Lua and Java targets. With testing, modifications to those .h files triggered regeneration of SWIG. Consequent builds when nothing changed properly did not regenerate and rebuild. I think this is now better than what we had with SCons. Other than that, I only included what headers were included from the .i files, and nothing further below that (files included in those files). I assume this is fine, but if we should run into a strange problem, at least we know what to fix. Thanks John for bring this up! steven On Fri, Apr 27, 2012 at 7:23 PM, Steven Yi |
Date | 2012-04-27 20:19 |
From | jpff@cs.bath.ac.uk |
Subject | Re: [Cs-dev] Not compiling |
The swig stuff is OK now (apparently) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |