Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-30 22:41, Hans-Christoph Steiner wrote: Having the name SHARED_SOURCE singular highlights that its a single file, which I think it should be. But since its an internal variable, I would be OK with it having a different name. i

Re: [PD-dev] how to load shared code for libraries

On Oct 31, 2011, at 4:53 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-30 22:41, Hans-Christoph Steiner wrote: Having the name SHARED_SOURCE singular highlights that its a single file, which I think it should be. But since its an internal

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-31 15:35, Hans-Christoph Steiner wrote: You should create some code that solves your issue in your library. Then we'll take it from there. hmm, the diff i posted was a cleaned up diff taken from iem/iemnet/Makefile. the code is

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/29/2011 04:35 PM, Hans-Christoph Steiner wrote: These things are really all by design. This makefile template is not trying to be all things to all people, but instead provide the easiest solution for 98% of the cases. By not handling

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/30/2011 09:13 PM, IOhannes m zmölnig wrote: it is exactly my suggestion to standardize it to lib$(LIBNAME).$(EXT). to be more precise, my suggestion basically contains exactly 2 suggestions: - - rename *_SOURCE to *_SOURCES (for

Re: [PD-dev] how to load shared code for libraries

On Oct 30, 2011, at 4:23 PM, IOhannes m zmölnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/30/2011 09:13 PM, IOhannes m zmölnig wrote: it is exactly my suggestion to standardize it to lib$(LIBNAME).$(EXT). to be more precise, my suggestion basically contains exactly

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/19/2011 01:29 AM, Hans-Christoph Steiner wrote: I committed the change to tkwidgets and the template/Makefile. i tried to use the new template/Makefile for this feature and noticed a few issues: - - object sources are called SOURCES, whereas

Re: [PD-dev] how to load shared code for libraries

On Oct 29, 2011, at 10:26 AM, IOhannes m zmölnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/19/2011 01:29 AM, Hans-Christoph Steiner wrote: I committed the change to tkwidgets and the template/Makefile. i tried to use the new template/Makefile for this feature and

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-19 18:33, Hans-Christoph Steiner wrote: Does it work for you? it seems to work ok. at least the objects are loading (though i get a lot of tcl/tk errors with some of the examples, but i guess that's unrelated to the main problem)

Re: [PD-dev] how to load shared code for libraries

On Oct 20, 2011, at 9:32 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-19 18:33, Hans-Christoph Steiner wrote: Does it work for you? it seems to work ok. at least the objects are loading (though i get a lot of tcl/tk errors with some of the

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-19 01:29, Hans-Christoph Steiner wrote: Yes! I got it working. I see the way to use it for this situation, this looks like great news! fgmadr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using

Re: [PD-dev] how to load shared code for libraries

On Oct 19, 2011, at 3:30 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-10-19 01:29, Hans-Christoph Steiner wrote: Yes! I got it working. I see the way to use it for this situation, this looks like great news! Does it work for you? .hc

Re: [PD-dev] how to load shared code for libraries

On Thursday, September 29, 2011 8:49 AM, IOhannes m zmölnig zmoel...@iem.at wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/28/2011 03:07 PM, Hans-Christoph Steiner wrote: Ah, ok, that changes things. So you are sure there isn't a way to make this work? on, i'm not

Re: [PD-dev] how to load shared code for libraries

On Tuesday, October 18, 2011 6:50 PM, Hans-Christoph Steiner h...@at.or.at wrote: On Thursday, September 29, 2011 8:49 AM, IOhannes m zmölnig zmoel...@iem.at wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/28/2011 03:07 PM, Hans-Christoph Steiner wrote: Ah, ok, that

Re: [PD-dev] how to load shared code for libraries

On Thursday, September 29, 2011 8:49 AM, IOhannes m zmölnig zmoel...@iem.at wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/28/2011 03:07 PM, Hans-Christoph Steiner wrote: Ah, ok, that changes things. So you are sure there isn't a way to make this work? on, i'm not

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/28/2011 03:07 PM, Hans-Christoph Steiner wrote: Ah, ok, that changes things. So you are sure there isn't a way to make this work? on, i'm not sure. i only reported issues i came across. If so, do you think there are other shared

Re: [PD-dev] how to load shared code for libraries

On Sep 29, 2011, at 2:49 AM, IOhannes m zmölnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/28/2011 03:07 PM, Hans-Christoph Steiner wrote: Ah, ok, that changes things. So you are sure there isn't a way to make this work? on, i'm not sure. i only reported issues i came

Re: [PD-dev] how to load shared code for libraries

On Sep 28, 2011, at 3:15 AM, IOhannes m zmoelnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-09-27 21:55, Hans-Christoph Steiner wrote: That's a good break down of the issues. I'll checkout @loader_path. The @executable_path technique has been in Pd-extended for a long

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2011-09-26 23:29, Hans-Christoph Steiner wrote: My guess is that it'll be something like this: #ifdef _WIN32 PATH #elif defined(__APPLE__) DYLD_LIBRARY_PATH #else LD_LIBRARY_PATH #endif i would go for something with less

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://cocoaconvert.net/2009/08/02/frameworks-with-private-frameworks/ fgmasdr IOhannes ___ Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev -BEGIN PGP SIGNATURE-

Re: [PD-dev] how to load shared code for libraries

That's a good break down of the issues. I'll checkout @loader_path. The @executable_path technique has been in Pd-extended for a long time, check out all of the libs in Pd-extended.app/Contents/lib by doing something like: otool -L

[PD-dev] how to load shared code for libraries

IOhannes and I were discussing how to load shared code for a libdir on IRC. The sticking point is that Mac OS X seems to require dylibs to have a hard-coded path. IOhannes posted a test lib to try to work out how to do it using DYLD_LIBRARY_PATH: http://iem.at/~zmoelnig/OSX/test.tgz

Re: [PD-dev] how to load shared code for libraries

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/26/2011 06:52 PM, Hans-Christoph Steiner wrote: IOhannes and I were discussing how to load shared code for a libdir on IRC. The sticking point is that Mac OS X seems to require dylibs to have a hard-coded path. IOhannes posted a test lib

Re: [PD-dev] how to load shared code for libraries

On Sep 26, 2011, at 2:42 PM, IOhannes m zmölnig wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/26/2011 06:52 PM, Hans-Christoph Steiner wrote: IOhannes and I were discussing how to load shared code for a libdir on IRC. The sticking point is that Mac OS X seems to require