push and dependencies
I'm trying to compile the current OS X version with push support.
I've installed push 3.1.0 into /usr/local (the rest of the dependent libraries are in /opt/ from MacPorts).
When I run the make, I get complaints about the .d dependency files. The first was that pushC.h couldn't be found, and I noticed that it wasn't installed into /usr/local/include
Placing it in there, now there are several other .h files that are missing as we get a little farther but balk at
kernel/internalFunctions/breveFunctionsPush.d
I figure I could just search around for the other push header files and put them in /usr/local/include, but was wondering if there was a 'best practices' with respect to building breve - for where they should live?
-fp
Edit- once I created a 'push' directory in /usr/local/include with the appropriate includes, the build starts but fails when we get around to building the push functions. I'm getting a versionitus feeling here?
remove kernel/internalFunctions/breveFunctionsPush.d
The *.d files are created at build time. Occasionally, if the build process fails (like it did the first time on the missing .h files), then bogus .d files will be left behind and the build won't work. Just remove the .d files and try the build again.
Also, some major changes have been made to Push rather recently, so the forthcoming version 2.6 of breve will include some big changes and updates. If you are building breve from the Subversion repository, I would recommend using the CVS version of Push as well. I can't say that the 2.6 breve source is 100% stable yet though, so proceed in that direction at your own risk!
- jon
OK- perfect. I started
I forgot to mention that I cleaned up the .d files when they errored. Seems like the issue is versions...
OK- perfect. I started building with the CVS push, but it too was a little unstable... all part of the fun.
OS X?
If you don't mind me asking what is the requirement to compile over the installer? I would keep eveything in the opt/ where macports .conf files reside, then make any changes.
I have not failed! I have only tried 100,000 ways that will not work. —Thomas Edison