07/02/2009 3:54 AM
.qnx_internal.mk and automated builds
I need to be able to take my IDE projects and build them from the command line.
However, it looks as though .qnx_internal.mk is being used by the IDE to do some fancy stuff with LIBS and other
Since .qnx_internal.mk is generated (or at least I understand it to be) by the IDE, we don't check these files into
source code control, and we don't deliver this file to the customer.
The customer needs to be able to build the projects from the command line w/o haveing to use the IDE. I also want to
keep from having to have two different common.mk files for command line vs IDE builds.
My question is, should this file .qnx_internal.mk be included in source code control?
Does it change with changes to build settings in the IDE? Or is this file pretty static?
It has some nice conventions in it, and I'd like to use it, but in the past, I've had to check out this file manually
when changing projects settings or other (now since forgotten) IDE operations.
Any insight into this would be helpful. I'm having a hard time making this work in a way that is a no-brainer for our