Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - Blank environment variables in post-build actions: Page 1 of 6 (6 Items)
   
Blank environment variables in post-build actions  
I want to add some post-build actions to my QNX Momentics static library project.  It seems like QNX_TARGET and VARIANT 
are blank while CPU and BUILDNAME are properly populated.  With the post build actions below I expected:

   c:\test1.txt = "libhutilcpp_g.a"
   c:\test2.txt = "armle"
   c:\test3.txt = "C:/proj/cf/trunk/target/qnx6/"
   c:\test4.txt = "-v7"

The test1.txt file contained what I expected.  The test2.txt file contained "arm" instead of "armle" even though my 
build variants was set to ARM v7 (Little Endian).  The test3.txt and test4.txt files were completly blank. 

#===== POST_BUILD - extra steps to do after building the image.
define POST_BUILD
-@echo $(BUILDNAME) > c:\test1.txt
-@echo $(CPU) > c:\test2.txt
-@echo $(QNX_TRAGET) > c:\test3.txt
-@echo $(VARIANT) > c:\test4.txt
-$(if $(filter AR, $(BUILD_TYPE)), @$(CP_HOST) $(BUILDNAME) $(QNX_TARGET)/$(CPU)$(VARIANT)/lib)
-@cp $(PROJECT_ROOT)/*.h $(QNX_TARGET)/usr/include
endef

The build products are all OK.  Any ideas on why these are blank would be appreciated.

 - Pete