Re: [AD] Allegro on OpenBSD

[Jon Rafkind <workmin@xxxxxxxxxx>]

Sorry it has taken me so long to get back to this..

>  
>
> > I removed the -f flag from the ps call in src/unix/usystem.c and
> > get_executable_name works fine now but I have another suggestion. Maybe
> > Im missing something but if the point of the function is to return the
> > current executable name why cant Allegro just combine getcwd() with
> > argv[0]? Allegro on Unix can already manipulate argv/argc via
> > src/unix/umain.c so why not steal argv[0] and stuff that into some
> > Allegro global variable?
> >    
>
> Because umain isn't used by default on UNIX (in other words, the UNIX port
> doesn't need END_OF_MAIN()) - so we don't have acces to argv[0]. It's
> possible to change this with a configure option (--enable-magicmain).
> If there's a different way to get the executable name under OpenBSD, I'd
> rather use that - otherwise the configure check could be adjusted to be
> active only when needed.
>
>  
I see in 4.2.0 beta 4 the changelog mentions get_executable_name is 
fixed for OpenBSD but its not really since OpenBSD is using the "ps" 
hack which doesnt work. Can I get a mention for finding this? :). Im 
looking into better ways to get the executable name in BSD but im not 
having a lot of luck.

> > BTW, the split_modex_screen symbol is still missing in CVS.
> >    
>
> I know, we haven't agreed on an ultimate solution yet. Can you try Peter's
> patch from yesterday and see if it works ok for you?
>  
Its been long enough that Peters patch seems to have been applied to CVS 
so I dont get a warning or anything about split_modex_screen anymore.

Just to keep my focus here are the remaining issues are:
1. linking with -lossaudio to get rid of the _oss_ioctl symbol not 
found. Should libossaudio be dynamically linked into the liballeg.so?
2. find a better way to get the executable name for BSD
3. Fix or remove OSS midi from BSD.