Le 20/08/2014 11:16, Nicolas Montgermont a écrit :
Hello,
Le 20/08/2014 10:07, IOhannes m zmoelnig a écrit :
conclusion:
add abstractions/ to your path, so you have a proper [gemwin].
IMHO, these abstractions should stand in the same path as the other
objects (ie next to the Gem.pd_xx)
i agree, the make install should copy them.
c
From the user point of view there is no difference between object that
are externals from the lib and objects that are abstractions that rely
on externals from the lib.
Atm, the abstractions achieve functionality that are really close to
other objects from gem, or even that used to be objects in Gem.
It means the compatiblity is broken just because of the displacements of
these objects in a new path ( ./abstractions)
Moreover, the management of path/lib is now cleaner directly in the
patch with [declare], it means someone has to [declare -lib Gem -path
Gem/abstractions] to get them, and as they cover the mandatory functions
of Gem (gemhead, gemwin) it makes the import of the library more complex
all the time.
If possible Gem should work with [declare -lib Gem], is there a proper
way to do that?
Best,
Nicolas
_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev
