QNX makefiles

Hi,

can i correctly avoid building of shared lib-s
in “so” directory (ie lib*S.a) ?

if i do in common.mk:

FULLNAME_SAR=
BUILDNAME_SAR=
INSTALLNAME_SAR=

after
include $(MKFILES_ROOT)/qmacros.mk
and before
include $(MKFILES_ROOT)/qtargets.mk

then thate file does not builds by “make” command (Ok),
but “make install” does output:

/bin/cp -vnfpc
cp: A source and destination must be specified.
make[2]: [qinstall] Error 1 (ignored)

Q: what is correct way to do that?
(or can i aviod this error message too?)

Thanks,
vasilii

vasilii <vv40in@rambler.ru> wrote:

can i correctly avoid building of shared lib-s
in “so” directory (ie lib*S.a) ?

if i do in common.mk:

FULLNAME_SAR=
BUILDNAME_SAR=
INSTALLNAME_SAR=

after
include $(MKFILES_ROOT)/qmacros.mk
and before
include $(MKFILES_ROOT)/qtargets.mk

then thate file does not builds by “make” command (Ok),
but “make install” does output:

You can stop it from building a little more cleanly by doing a:

POST_TARGET=

after qmacros.mk and before qtargets.mk, but there’s really no
way to stop it from trying to install. May I ask why you don’t want
it created?

\

Brian Stecher (bstecher@qnx.com) QNX Software Systems, Ltd.
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8

vasilii <vv40in@rambler.ru> wrote:

Hi,

can i correctly avoid building of shared lib-s
in “so” directory (ie lib*S.a) ?

Is the thing your are building a “library” ?
If it is, you will need the lib*S.a (for linking
other application).
If it is not, (you just try to build a shared
object), you should call your directory “dll”
instead of “so”.

-xtang

if i do in common.mk:

FULLNAME_SAR=
BUILDNAME_SAR=
INSTALLNAME_SAR=

after
include $(MKFILES_ROOT)/qmacros.mk
and before
include $(MKFILES_ROOT)/qtargets.mk

then thate file does not builds by “make” command (Ok),
but “make install” does output:

/bin/cp -vnfpc
cp: A source and destination must be specified.
make[2]: [qinstall] Error 1 (ignored)

Q: what is correct way to do that?
(or can i aviod this error message too?)

Thanks,
vasilii