[Cs-dev] an interesting compile warning
Date | 2005-03-09 21:44 |
From | Matt Ingalls |
Subject | [Cs-dev] an interesting compile warning |
on OSX in dlfcn.h: #warning "You are using dlopen(), a legacy API. Please use the Mach-O dylib loading APIs if at all possible" ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-03-10 09:11 |
From | Victor Lazzarini |
Subject | Re: [Cs-dev] an interesting compile warning |
dlopen() will be compatible with Linux etc, whereas the Mach-O APIs aren't (I'm pretty sure but not totally). That'll mean we'll have to use specialised code. Victor At 21:44 09/03/2005, you wrote: >on OSX in dlfcn.h: > >#warning "You are using dlopen(), a legacy API. Please use the Mach-O >dylib loading APIs if at all possible" > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Csound-devel mailing list >Csound-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/csound-devel Victor Lazzarini Music Technology Laboratory Music Department National University of Ireland, Maynooth ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-03-10 12:25 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | [Cs-dev] dlopen usage in csound/load_opcode.c |
In Csound 4, csound/load_opcode.c has an "interesting" structure. It looks like: ------------------ load_opcode.c ------------------ Intro #if defined(WIN32) Windows specific code #elif defined(LINUX) || defined(NETBSD) || (__MACH__) Platform independent code using dlopen #elif defined(MACOSX) MacOS X specific code using routines that start with NS #else Dummy routines #endif Stuff that uses the above ------------------ load_opcode.c ------------------ Does the defined(MACOSX) branch ever get used? Also, shouldn't this code be rewritten to use dlopen whenever it's available? In other words, shouldn't this code be rewritten to have the following form: ------------------ alt load_opcode.c ------------------ Intro #if define (HAVE_DLFCN_H) || defined(LINUX) || defined(NETBSD) || (__MACH__) Platform independent code using dlopen #elif defined(WIN32) Windows specific code #elif defined(MACOSX) MacOS X specific code using routines that start with NS #else Dummy routines #endif Stuff that uses the above ------------------ alt load_opcode.c ------------------ John Victor Lazzarini |
Date | 2005-03-10 15:11 |
From | Anthony Kozar |
Subject | Re: [Cs-dev] dlopen usage in csound/load_opcode.c |
I noticed that GBS was using this code recently. My impression was that the load_opcode.c code is not used and that dl_opcodes.c should be used instead. The latter is where I added my OS 9 code for loading libraries but the OS X-specific code is only in load_opcodes.c *shrug* Anthony On 3/10/05 7:25 AM, John D. Ramsdell |
Date | 2005-03-10 15:50 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | Re: [Cs-dev] dlopen usage in csound/load_opcode.c |
Anthony Kozar |
Date | 2005-03-10 18:20 |
From | matt |
Subject | Re: [Cs-dev] dlopen usage in csound/load_opcode.c |
oh really? i use load_opdcode -- what does cs5 use? On Mar 10, 2005, at 7:50 AM, John D. Ramsdell wrote: > Anthony Kozar |
Date | 2005-03-10 18:59 |
From | jpff@cs.bath.ac.uk |
Subject | Re: [Cs-dev] dlopen usage in csound/load_opcode.c |
I wrote that code -- on 10.2 which I run there is no sign of dlopen -- and hence the code. Actually I think changes in CS4 shouydl just not happen, and energy put into CS5. ==John ffitch ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-03-10 19:13 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | Re: [Cs-dev] dlopen usage in csound/load_opcode.c |
jpff@cs.bath.ac.uk writes: > I wrote that code -- on 10.2 which I run there is no sign of dlopen > -- When I compile on 10.3, the code compiles and links, so dlopen is there. I don't know if it works, but Mac developer documentation suggested to me it should. John ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
Date | 2005-03-12 23:22 |
From | ramsdell@mitre.org (John D. Ramsdell) |
Subject | Re: [Cs-dev] dlopen usage in csound/load_opcode.c |
Kelly Fitz reports that on a Mac, he is able to load his opcodes on one machine using the GBS distribution. However, on a similar machine, the same system has trouble dynamically loading the FFTW library. I'm not sure about FFTW problem, but this all suggests that dlopen works on Macs. I rearranged the code in load_opcodes.c as I suggested earlier. This change will have no impact on non-GBS distributions of Csound 4. John ramsdell@mitre.org (John D. Ramsdell) writes: > In Csound 4, csound/load_opcode.c has an "interesting" structure. It > looks like: > > ------------------ load_opcode.c ------------------ > Intro > > #if defined(WIN32) > > Windows specific code > > #elif defined(LINUX) || defined(NETBSD) || (__MACH__) > > Platform independent code using dlopen > > #elif defined(MACOSX) > > MacOS X specific code using routines that start with NS > > #else > > Dummy routines > > #endif > > Stuff that uses the above > ------------------ load_opcode.c ------------------ > > Does the defined(MACOSX) branch ever get used? Also, shouldn't this > code be rewritten to use dlopen whenever it's available? In other > words, shouldn't this code be rewritten to have the following form: > > ------------------ alt load_opcode.c ------------------ > Intro > > #if define (HAVE_DLFCN_H) || defined(LINUX) || defined(NETBSD) || (__MACH__) > > Platform independent code using dlopen > > #elif defined(WIN32) > > Windows specific code > > #elif defined(MACOSX) > > MacOS X specific code using routines that start with NS > > #else > > Dummy routines > > #endif > > Stuff that uses the above > ------------------ alt load_opcode.c ------------------ > > John > > Victor Lazzarini |