[Clam-devel] includes
Greg Kellum
greg.kellum at gmail.com
Sun Nov 4 15:09:24 PST 2007
Hi Pau,
Well, I did use a command like g++ -I/usr/include/ file.cxx, except
my files were in /usr/local/include. And it worked fine for headers
whose include statements looked like this:
#include "XMLStorage.hxx"
But the compiler threw errors everytime it encountered an includes
statement in one of those headers that looks like this:
#include <CLAM/XMLStorage.hxx>
When I replaced these includes with includes like the one above, then
everything worked fine. BUT there are a LOT of those <CLAM/
ClassName.hxx> include statements. You don't much like those anyway
if I remember correctly. What do you think about me writing a python
script to convert them to the first format?
By the way I did correct all the XML config files in the test
directory. Everything should work fine now once you update to the
newest data. Let me know if it doesn't.
Best,
Greg
On Nov 4, 2007, at 10:34 PM, Pau Arumí wrote:
>
> On dg, 2007-11-04 at 20:59 +0100, Greg Kellum wrote:
>> Hi,
>>
>>
>> I've been working on a Max/MSP plugin that accesses CLAM by binding
>> against the CLAM library. I've been working in XCode which of course
>> just calls g++ to compile and build things, and one problem that I've
>> been having is dealing with the CLAM include statements which are in
>> the form <CLAM/ClassName.hxx>. Did you have to add any options in
>> scons to get g++ to handle these correctly? I'm wondering what
>> flag I
>> would have to give g++ to get it to deal with these in the same way
>> that it does when called from scons.
>>
>
> This should be simple. Say, you installed clam in the default dirn
> (/usr), the all headers have been copied into /usr/include/CLAM/, and
> the compilation command should be something like
> g++ -I/usr/include/ file.cxx
>
> and for any install_prefix:
> g++ -Iinstall_prefix/include/ file.cxx
> Another tip: clam and networkeditor scons allow the verbose=1
> parameter.
> Then it shows the g++ command being issued.
>
>> P.S. By the way Pau, you can throw away all of the classes in the
>> plugins/continuousExcitationSynthesizer/toreview folder.
>
> Ok thanks.
> And tell us if you fix the xml needed for the streaming
> (networkeditor)
> synthesizer.
>
> Pau
>
>
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-
> devel
More information about the clam-devel
mailing list