Writing new objects

From 4f5f017bdf452419ad396346bacad623acb0f41c Mon Sep 17 00:00:00 2001 From: Travis CI Date: Thu, 9 May 2019 20:32:44 +0000 Subject: Gem 01b1861db023a225d01a4d5a519cf54f09f631f5 osx/i386 built 'master:01b1861db023a225d01a4d5a519cf54f09f631f5' for osx/i386 --- Gem/manual/WriteCode.html | 82 +++++++++++++++++++++++------------------------ 1 file changed, 41 insertions(+), 41 deletions(-) (limited to 'Gem/manual/WriteCode.html') diff --git a/Gem/manual/WriteCode.html b/Gem/manual/WriteCode.html index d4d0480..1fb8e30 100644 --- a/Gem/manual/WriteCode.html +++ b/Gem/manual/WriteCode.html @@ -1,41 +1,41 @@ - - - - - - - Writing new objects - - - - -

-Creating new GEM objects

-Look at the source code :-) GEM is written in C++, which means that -you have to jump through some hopes to interact properly with Pd, which -is written in C. If you look in Base/CPPExtern.h, you will see a -collection of macros which you can use to help you create new objects. -Use one of the GEM objects which is closest to what you want to do as a -template. -

One problem on SGI...you will need to -

setenv LD_LIBRARY_PATH "/where/ever/pd/gem" -

so that rld (the run-time linker) can find the GEM dso. Because -you are linking with GEM, Pd isn't involved with the run time linking process; -it is all done when Pd calls dlopen. -

On NT, there is much the same problem... -

set your PATH environment variable to \where\ever\pd\gem -

or -

make sure that your new .dll is located in the same directory where -GEM is. -

On NT, all of the classes and functions are exported through declexport/declimport. -You shouldn't have to do anything to call the functions. I have not -had any problems making other dll's which are loaded into Pd at runtime. -You need to make certain that you are exporting the correct functions. -If your dll cannot find the gem.dll, then it will silently fail. -

And of course, e-mail IOhannes m zmölnig (zmoelnig@iem.at) if you have any problems, -questions, or solutions -

[return] -
- - + + + + + + + Writing new objects + + + +

+Creating new GEM objects

+Look at the source code :-) GEM is written in C++, which means that +you have to jump through some hopes to interact properly with Pd, which +is written in C. If you look in Base/CPPExtern.h, you will see a +collection of macros which you can use to help you create new objects. +Use one of the GEM objects which is closest to what you want to do as a +template. +

One problem on SGI...you will need to +

setenv LD_LIBRARY_PATH "/where/ever/pd/gem" +

so that rld (the run-time linker) can find the GEM dso. Because +you are linking with GEM, Pd isn't involved with the run time linking process; +it is all done when Pd calls dlopen. +

On NT, there is much the same problem... +

set your PATH environment variable to \where\ever\pd\gem +

or +

make sure that your new .dll is located in the same directory where +GEM is. +

On NT, all of the classes and functions are exported through declexport/declimport. +You shouldn't have to do anything to call the functions. I have not +had any problems making other dll's which are loaded into Pd at runtime. +You need to make certain that you are exporting the correct functions. +If your dll cannot find the gem.dll, then it will silently fail. +

And of course, e-mail IOhannes m zmölnig (zmoelnig@iem.at) if you have any problems, +questions, or solutions +

[return] +
+ + -- cgit v1.2.1