Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

Re: SDL/GL(UE) on Darwin
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 31 Jul '07

31 Jul '07

> It should be enough to call Public.ObjectiveC.purge_autorelease_pool > () both in init() and exit(). Ah, that sounds nice. I seem to have lost the well defined behaviour of getting mentioned errors now, both with and without these calls, but I still get crashes in GL code, though without all the ahead of time warnings on stderr. Must be something else in my environment that has changed I guess, though I can't figure out quite what. > If you are creating multiple threads, the there's additional work > that needs to be done, but I'll spare you the details if you're not > using them. We do, but only the backend thread gets to run any GL (SDL) code (as some GL libraries are finicky about that kind of thing). I'm not sure if that means I get the additional work burden or not. > Incidentally, some of my code from the ObjectiveC module came in > handy when I was trying to set up callbacks from the USB subsystem... > I had already put support for running the OSX NSRunLoop in the Pike > backend, which makes the callbacks and all kinds of other > functionality possible, like Bonjour queries and Distributed > Objects... pretty nifty stuff. > > Bill

1 0

Re: SDL/GL(UE) on Darwin
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 30 Jul '07

30 Jul '07

> I guess a more fundamental question is: does SDL on Darwin imply > Cocoa? That's anyone's guess, but that's the impression I got from the tip page. Lots of people seem to have run into this error with SDL, and that was the only page I came up with that offered anything remotely looking like a solution. I'm only using the SDL (via GLUE) pike bindings on an OS agnostic application (aido), but it presently does not work on my macbook, so I've been chasing the issues. Even getting a minimal GLUE app not to crash would be good progress: #! /usr/local/bin/pike77 int main() { GLUE.init( (["title":"Glue example"]) ); draw_frame(); return -1; } void draw_frame() { call_out(draw_frame, 0.02); do_gl_code(); GLUE.swap_buffers(); } void do_gl_code() { GLUE.draw_line( 1.0, 1.0, 1.5, 1.5, Image.Color.red ); }

2 2

error: `LIBS' was not set in the previous run
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 30 Jul '07

30 Jul '07

Has anyone else seen this problem? When building current 7.7 from scratch, it bombs out during the configuration of CommonLog: configure: loading cache ../.././config.cache configure: error: `LIBS' was not set in the previous run configure: error: changes in the environment can compromise the build In config.cache there is the following: ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= (these are the only ac_env/ac_cv_env entries). Maybe this is related to the line LIBS= in PIKE_RETAIN_VARIABLES somehow? Interestingly enough, the problem does not occur on my PS3, which also has ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= in config.cache...

3 8

file_peek and async_connect
by Arne Goedeke ＠ Pike developers forum 30 Jul '07

30 Jul '07

I found some strange behaviour using async_connect when connecting to unbound ports on localhost. The callback is never called. Try something like this: void cb(mixed ... args) { write("cb: %O\n", args); } int main () { object o = Stdio.File(); o->async_connect("127.3.3.5", 3245, cb); return -1; } A reason I found for that (not sure if there are more issues, it fixes this problem though) is that 1) in __stdio_close_callback() read(0,1) is used to check if data can be read from the socket instead of peek(). 2) file_peek() does not check for POLLERR or POLLHUP and therefore returns true even if the socket has been closed or some error occured using peek() instead of read(0,1) in __stdio_close_callback() and adding }else if (fds.revents & (POLLERR | POLLHUP)){ ret=0; to file_peek() fixed this issue for me. The same problem may occur when using select() in file_peek(), I did not test that though. arne

6 13

SDL/GL(UE) on Darwin
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 29 Jul '07

29 Jul '07

I've been looking into running a GLUE application under OS X, and hit the error described on http://www.ogre3d.org/wiki/index.php/MacLibrary (a slew of NSAutreleasepool warnings followed by a "*** Uncaught exception: <NSInternalInconsistencyException> Error (1002) creating CGSWindow") and a crash in SDL.set_video_mode on its first glGet call. This (completely naïve) approach based on the suggestions offered did not seem to do much good: Index: src/post_modules/SDL/SDL.cmod =================================================================== RCS file: /pike/data/cvsroot/Pike/7.7/src/post_modules/SDL/SDL.cmod,v retrieving revision 1.29 diff -u -r1.29 SDL.cmod --- src/post_modules/SDL/SDL.cmod 12 Nov 2005 20:37:07 -0000 1.29 +++ src/post_modules/SDL/SDL.cmod 29 Jul 2007 21:07:04 -0000 @@ -151,6 +151,13 @@ *! */ PIKEFUN void init(int flags) { + /* init needed on XDarwin: http://www.ogre3d.org/wiki/index.php/MacLibrary */ + void* cocoa_lib; + cocoa_lib = dlopen( "/System/Library/Frameworks/Cocoa.framework/Cocoa", RTLD_LAZY ); + void (*nsappload)(void); + nsappload = (void(*)()) dlsym( cocoa_lib, "NSApplicationLoad"); + nsappload(); + if( SDL_Init(flags) == -1) { Pike_error("SDL Initialization failed: %s\n", SDL_GetError()); }

1 0

peek changes
by Peter Bortas ＠ Pike developers forum 29 Jul '07

29 Jul '07

Current non-compilation status of 7.7 on Debian Etch: Compiling modules/files/file.c /home/peter/hack/Pike/7.7/src/modules/files/file.c: In function $B!F(Bfile_peek$B!G(B: /home/peter/hack/Pike/7.7/src/modules/files/file.c:860: error: $B!F(Bfd$B!G(B undeclared (first use in this function) /home/peter/hack/Pike/7.7/src/modules/files/file.c:860: error: (Each undeclared identifier is reported only once /home/peter/hack/Pike/7.7/src/modules/files/file.c:860: error: for each function it appears in.) /home/peter/hack/Pike/7.7/src/modules/files/file.c:864: error: $B!F(BPD$B!G(B undeclared (first use in this function)

2 1

Monger
by Peter Bortas ＠ Pike developers forum 28 Jul '07

28 Jul '07

Monger still gives a backtrace if you try to query a nonexistent module. Would be nice to have fixed before the next stable and should be easy to fix for anyone that has 10min free. Example: % pike -x monger --query gazonk No such module gazonk. /usr/local/pike/7.6.117/lib/modules/Tools.pmod/Monger.pmod/MongerUser.pike:428: Tools.Monger.MongerUser()->xmlrpc_handler()->_caller()->`()("gazonk") /usr/local/pike/7.6.117/lib/modules/Tools.pmod/Monger.pmod/MongerUser.pike:196: Tools.Standalone.monger()->get_module_action_data("gazonk",0) /usr/local/pike/7.6.117/lib/modules/Tools.pmod/Monger.pmod/MongerUser.pike:165: Tools.Standalone.monger()->do_query("gazonk",0) /usr/local/pike/7.6.117/lib/modules/Tools.pmod/Monger.pmod/MongerUser.pike:123: Tools.Standalone.monger()->main(3,({"/usr/local/pike/7.6.117/lib/modules/T ools.pmod/Standalone.pmod/monger.pike","gazonk"}))

2 2

Re: [Announce] Pike: an Introduction now available
by Jonas Walld�n ＠ Pike developers forum 25 Jul '07

25 Jul '07

Speaking of that, one not-so-minor cosmetic detail that I'd like to see changed in the book is the page header font size. Right now it is very big which causes the headers to look like section titles in the main flow of the text. This has confused me more than once when browsing Grubba's copy. For an example, look at http://www.lulu.com/browse/preview.php?fCID=78730 and navigate to, say, page 2. (FYI, while looking at the web preview I noticed a typo on page iv: "Institionen" -> "Institutionen".)

2 1

Re: [Announce] Pike: an Introduction now available
by Jonas Walld�n ＠ Pike developers forum 25 Jul '07

25 Jul '07

1 0

[Announce] Pike: an Introduction now available
by H.William Welliver III 25 Jul '07

25 Jul '07

[My apologies for the double posting. I was apparently too excited to include a subject in my previous post. ] Good evening Pike fans, We're pleased to announce the immediate availability of Pike: An Introduction. Three years in the making, Pike: An Introduction is the definitive introduction to the Pike programming language. Weighing in at almost 300 pages, the book contains numerous examples which coincide with topics of discussion, as well as a chapter on the basics of several popular modules. Proceeds from sales of Pike: An Introduction will be used to help fund Pike development and marketing. That means that, in addition to getting up to speed on your favorite programming language, you'll also be helping to advance and promote Pike. We expect the book to be available at online outlets such as Amazon or Barnes and Noble in about a month. Until then, you can get your copy from Lulu, our printing vendor for USD 29.95. In addition to getting your book sooner, Lulu's commissions are lower, meaning that a larger percentage of your purchase price will be made available for supporting the Pike community. Learn more about the book, and purchase your copy today by visiting: http://book.gotpike.org/ As always, your comments and suggestions are welcome! Best, Bill Welliver and Martin Bähr, editors !DSPAM:469c3c07195971412658825!

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel