[PD-dev] pd buildsys: libdir / etags and the existing template

[mescalinum at gmail.com]

>> i'm not familiar with etags, i understand that

never heard about etags, only know about ctags (Exhuberant Ctags:
http://ctags.sourceforge.net/)
vim supports ctags natively

>> dist seems useful, should there be an install
>> directive too, and perhaps some meta data with the
>> relevant environment vars which the lib was built.
>>
>> obviously this template needs to be twisted a
>> little for existing libs, but i was also thinking
>> that there should be some extra vars for
>> additional cflags / ldflags / etc.. as it seems
>> a little too simplistic in its current state?

yep.
some notes about vars:

1) always respect what environment vars are. i.e. don't override CFLAGS,
LDFLAGS.... eventually accept additional CFLAGS as a parameter, that
allows overriding flags defined in Makefile.

examples:

bad:    CFLAGS = -fomit-frame-pointer -DPD
good:   CFLAGS += -fomit-frame-pointer -DPD

better: CFLAGS += -fomit-frame-pointer -DPD $(MORE_CFLAGS)
allows overriding some flag, example: make
MORE_CFLAGS="-fno-omit-frame-pointer"

2) don't put architecture dependant flags, or optimization flags. if you
have to put optimization flags, always allow to override them like
described above with $(MORE_CFLAGS)

examples:

bad: CFLAGS += -mcpu=crtex-m3
bad: CFLAGS += -march=nocona

3) always respect DESTDIR in install. it costs you nothing and is
transparent for those not using it.

example:

install:
    install ... $(LIB)  $(DESTDIR)/usr/lib/pd/extra/...

>
> configure.in/Makefile.in template for more complicated build
++

are you writing some ac/am macros specific to pd as well?


ciao


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20090913/d69ce77c/attachment.pgp>