I was wondering what the status was of embedding that was being worked on by a few people. I was wondering if it would be possible to get a status, and maybe a look at the code (even if it's non-working)
Bill
I think it's working, except for the fact that last time I tried to compile it, the makefiles broke. :( You could probably fix that by just manually working around it, but I didn't look in to it at that time.
I don't suppose there's any chance of getting a tarball of your work?
Bill
On Wed, 10 Aug 2005, Marcus Agehall (PacketFront) @ Pike (-) developers forum wrote:
I think it's working, except for the fact that last time I tried to compile it, the makefiles broke. :( You could probably fix that by just manually working around it, but I didn't look in to it at that time.
My work, no. You don't want it anyway... ;)
I would suggest just using the current CVS version and using the embedded-option to confiure. (Don't remember the exact name right now)
If you have some use for embedding Pike right now, that ought to be more then enough motivation for you to tinker enough with the makefiles to make it compile.
Then, you will probably have to write your own master etc, since you may or may not want to include all functionallity of Pike, but that is a whole different story. Start by just making the lib compile.
As a final note: It was a few months since my last attempt to compile it. Maybe Grubba has fixed the problem already, assuming it's not my compile-setup that was broken...
Embedded pike would be highly useful for macos-X.
Then one could easily make a SDL-wrapper-pike for UI-applications, and a 'normal' pike for normal programs.
Background: SDL requires it's own main() function to be used.
Embedded pike would be highly useful for macos-X.
Then one could easily make a SDL-wrapper-pike for UI-applications, and a 'normal' pike for normal programs.
Background: SDL requires it's own main() function to be used.
I assume you're referring to --with-libpike, right? I looked through the code, and its effects seem to be limited to the configure script. There also seems to be a target for libpike.o, but I don't see any source for that. Is this what you're referring to when you say there are makefile problems?
Bill
I would suggest just using the current CVS version and using the embedded-option to confiure. (Don't remember the exact name right now)
If you have some use for embedding Pike right now, that ought to be more then enough motivation for you to tinker enough with the makefiles to make it compile.
Then, you will probably have to write your own master etc, since you may or may not want to include all functionallity of Pike, but that is a whole different story. Start by just making the lib compile.
As a final note: It was a few months since my last attempt to compile it. Maybe Grubba has fixed the problem already, assuming it's not my compile-setup that was broken...
Yes, that is what I'm referring to.
All the code is in the regular files. All that is needed to turn Pike into a lib, are a few defines...
The major problem, that may or may not still exist, is that most pike symbols are exported and will pollute the namespace. It may or may not be a problem, depending on the application.
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
Marcus Agehall (PacketFront) ＠ Pike (-) developers forum -
Per Hedbor () ＠ Pike (-) developers forum
-
Xavier Beaudouin