Perhaps, but then we hit multiple "defined but not used" errors, due to the
"static" usage. Which complicates the warning configuration (if old swig,
change warning flags?)
And, of course, since it's in a header, it has to be static or the link fails.
/tried it all
-K
- Original Message
It occurs to me there may be #defines you could key off when swig runs so
you could just remove the inline portion for swig.
--Rafael
On Wed, Feb 20, 2013 at 9:17 AM, Rafael Schloming wrote:
> Sounds reasonable to me.
>
> --Rafael
>
>
> On Wed, Feb 20, 2013 at 8:31 AM, Ken Giusti wrote:
>
>> F
Sounds reasonable to me.
--Rafael
On Wed, Feb 20, 2013 at 8:31 AM, Ken Giusti wrote:
> Fails to build on Centos-5 with a swig parse error (Syntax error on
> input(1)).
>
> Details:
>
>swig-1.3.29-2.el5
>
>chokes on the definition of pn_dtag() in include/proton/engine.h:75 -
> specifical
Fails to build on Centos-5 with a swig parse error (Syntax error on input(1)).
Details:
swig-1.3.29-2.el5
chokes on the definition of pn_dtag() in include/proton/engine.h:75 -
specifically does not like the "inline" specifier.
I can "fix" it by:
1) remove "inline"
2) conf
Source is here:
http://people.apache.org/~rhs/qpid-proton-0.4rc1/
Java binaries are here:
https://repository.apache.org/content/repositories/orgapacheqpid-239/
This is the first release after some significant build system changes, so
don't be surprised if there are a few kinks to work out. Pl
