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

IOhannes m zmölnig zmoelnig at iem.at
Sun Oct 30 21:13:58 CET 2011


-----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 that 2%, it can be make much simpler for everyone else.  
> 
> - SHARED_SOURCE is lib$(LIBRARY_NAME).c, if you need multiple files, you need to modify things

but why is it then that the SHARED_SOURCE is assigned with "?=",
indicating that the user should be able to set the files to whatever
fits their needs?

why is it not documented?


> 
> - the shared lib name is deliberately standardized, therefore its not settable

the thing is, it is _not_ standardized,
it uses whatever SHARED_SOURCE is set to (and replaces .c by .$EXT),
which is settable, and therefore can be set to multiple source files,
making the template/Makefile simply not work.

it is exactly my suggestion to standardize it to lib$(LIBNAME).$(EXT).

> 
> This means that a dev can easily tell whether a lib contains a shared lib, and where its source code is.  Its self-documenting once you know it.  You just look at the file system, and you know where things are.

what is wrong with my suggestions?
i really have the feeling, that it is mainly rejected because the
suggestion comes from me (e.g. "not trying to be all things to all
people" basically boils down to "please don't fit into IOs little world")


mfgasdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6tsAIACgkQkX2Xpv6ydvTTAQCgzDzTF5H8kD2m6tC1z86qZJBU
z2UAnjvqmqUEepOu15iRGSMCf2SRuwLc
=T8AA
-----END PGP SIGNATURE-----



More information about the Pd-dev mailing list