FlashBuilder Debug Configurations

Similar Questions

• Flash Builder 4.7 Debug Configuration Bug

  I just updated today to Flash Builder 4.7 and came across an annoying bug that does not exist with 4.6. I always get many debug configurations when developing mobile applications, IE. iPhone, iPad, iOS on the device. When I tried to create these configurations this morning, I noticed that it doesn't let me have several configurations of AIR Simulator for various devices. When I change the device on one, it changes the device on the other, both of them doing exactly the same behavior. Everyone knows about this problem? Is there a way around it?

  There is a solution to this problem. To understand workaround, it will be good to understand a little better what is happening with the bug.

  As a result, the problem with this bug is not with the loading or saving of configurations, but rather with a switching between them. It seems that when switching between the two the same (for example, two configurations of Mobile Application), is not properly clear the form data, and because the form is not allowed to go out it does not correctly load the new information in and as such extends the old information. Since the recording of the code still works very well, when you exit it will record the messed up new configuration during the setup of old, good.

  So, technically, it is not the same configuration appears twice, but rather two different configurations which are set up the same because the form did not clearly get out when you switch between the two configurations.

  So now that we have a better understanding of the bug, here's workaround: If you click on something that uses a different form, it will destroy the shape. So for instance, if you have an iPhone 4 and an iPad Simulator Simulator and you have the iPad Simulator selected and you select the iPhone 4 Simulator, first simply click on the Mobile Application and then click on your iPhone 4 Simulator. When you do this all works very well.

  In addition, if you switch directly between the two, know that the configuration you just left is fine. It is only the one that you are currently looking that is messed up, and all you have to do is difficulty that you are looking for.

  So that at least we'll you work around the problem. It is also appropriate to establish just enough different configurations for where you never really need access the menu Debug Configurations. For example, I have two configurations set in place for each device or Simulator that I put in place, one who has the box 'Clear application to each launch data' verified and who does not. In addition, I have four simulators (iPad, iPhone, Android phone, Android Tablet) and one "on the device" installation (Android). Combining these gives me ten different configurations which covers the majority of what I do regularly and it does in so that I don't have need access Configurations Debug menu all that often.

  At this point with that many configurations it is also useful to organize all these configurations in the drop of debugging using the Organize favorites that can be selected in the drop-down list even.

  So, this made for a very long answer, but I hope that it will help you and help out some other people who also run in the same question. It does not change the fact that there is a really horrible bug and Adobe really needs to get on fixing it, but it can at least make sure it can be lived with.

• Password field Flash Builder 4.5 No. in the debug configuration.

  Hello

  I was going through the steps to deploy and debug an application on the SIM playbook, and I'm at the point where I have to put a password in flash Builder, but there is no place to put a password. I have the flash builder 4.5 installed. Any ideas why the password field is missing? I tried to make a connection with the SIM anyway and got an error Error: Missing argument - password

  Thanks in advance.

  I had the same problem. The solution for me was quite simple: try to resize the small window a bit bigger and your password field appears

• Debug configuration ID

  Hello
  
  We use identifiers to access a archive of Documaker and generate PDF files. For the purposes of debugging, I need to have a look at the NAFILE and the POLFILE created by IDS with access to archive. I found this option works:
  
  [Attachments]
  Debug = Yes
  
  I have 2 problems:
  1. the NAFILE and the POLFILE are left on the hard drive until it as deleted manually. Y at - it a timer option, I could set up so that files are automatically deleted after X minutes?
  2. the files are created under the DOCSERV folder. Y at - it an option that I could use to specify a different path for files?
  3. is there a cheat sheet for the INI options available for the ID? I found a manual that says I should use thsis format:
  [Debug]
  Attachments = Yes
  
  which is the exact opposite of what I have in my PAD. INI file.
  
  Thank you
  
  Gaëtan

  Sorry for the late reply... working holiday and pointing at all... :)

  Usually with versions more recent ID, you can specify paths in INI options, but the names of files, especially for temporary files, will almost always GUID generated by IDS. The parts of the bridge Documaker copy data of NA / POL must adhere to the < data=""> INI options well, so by using these settings is indeed correct. Your options for self-suppression of these files must either have an external process (e.g. cron, scheduled, or similar task) that deletes old files on a regular basis, or if you want to be stylish, you could write a custom rule of Identifications that adds the debug files to files temp to the purge list.

  The reason why ID does do this automatically is just as you would expect - it's a debug file and probably if you have enabled debugging, you want the file to stay around :) in the opposite case, debugging should be disabled because it is detrimental to performance.

  -Andy

• Eclipse: Choose my twice Debug Configuration to debug my application doesn't sound right.

  
  

  Fixed!

  Well... the problem was to have an illegal character in the label of the .cod file.

• Impossible to get anything it either appears in the Simulator

  Hello

  Despite the great "getting started" documentation and webcasts, can't do the Simulator to work...

  I can ping, and I don't get any errors when I chose a configuration of Flash Builder series - it generates the .bar file well and gives me the following output:

  Using icon: C:\Documents and Settings\aperryman\My Documents\_UI\PlayBook Tutorial\FB_PlayBookTest\bin-debug\BB_icon_72.pngThe bar manifest file is valid.Package created: C:\Documents and Settings\aperryman\My Documents\_UI\PlayBook Tutorial\FB_PlayBookTest/PlayBookTest.barAction: Install and LaunchFile size: 145772Installing com.amp.PlayBookTest.testLlBsYXlCb29rVGVzdCAgICA...actual_dname::com.amp.PlayBookTest.testLlBsYXlCb29rVGVzdCAgICAactual_id::testLlBsYXlCb29rVGVzdCAgICAactual_version::result::
  

  But it stops there and nothing is displayed in the Simulator.

  When I do a Debug launch, it's the same thing, except that I finally get a time-out error because it cannot connect to the debugger - probably not surprising.

  When I package and deploy via the command line, I get even a promising "done" at the end:

  C:\Documents and Settings\apman\My Documents\PlayBook Tutorial\FB_PlayBookTest\bin-debug>blackberry-airpackager -package PlayBookTest.bar -installApp -launchApp PlayBookTest-app.xml PlayBookTest.swf BB_icon_72.png -device 192.168.223.128Using icon: C:\Documents and Settings\apman\My Documents\PlayBook Tutorial\FB_PlayBookTest\bin-debug\BB_icon_72.pngThe bar manifest file is valid.Package created: PlayBookTest.barAction: InstallFile size: 145776Installing ...actual_dname::actual_id::actual_version::result::[-launchApp, -package, PlayBookTest.bar, -device, 192.168.223.128]Action: LaunchLaunching com.amp.PlayBookTest.bXAuUGxheUJvb2tUZXN0ICAgICA...done
  

  but nothing in the Simulator.

  The app is just the sample helloWorld application and works very well when I compile it as desktop AIR application.

  I'm on Windows XP and I don't have the admin rights.

  Does anyone have an idea what else could be wrong?

  Thank you very much

  Anna

  Finally got it works!

  Apparently not that if anyone else had the same problem, but just in case, here is what does the job:

  I just made a deployment command line with the flag set - devMode (without it I got the same results with Flash Builder or blackberry-airpackager, i.e. no error, but nothing appearing in the Simulator):

  >blackberry-deploy -installApp -devMode -device 192.168.223.128 -package PlaybookTest.bar
  

  And the strange thing is: now that it's installed, I'm able to run my FlashBuilder debug configuration and it installs and launches new construction without problems!

  Anyway, thanks again to all who have tried to help - I learned a few things along the way...

  Anna

• Debug with FlashBuilder 4.5 and Playbook simulator mode

  I use falshBuilder 4.5 and the last Playbook Simulator (July 2011).

  I am able to run the application on the Simulator. However, when I use the Debug mode, I get error on the Simulator as well as on the FlashBuilder. On the playibook Simulator, it says unable to connect.

  I use the IP address of the Simulator (like RUN works very well). Also I use debug by default IP configuration of the host defined in the Debug configuration.

  Has anyone faced similar problem. Something else must be set for this?

  Thank you.

  Hi all

  Finally I got it to work. I was using the wrong host debug after changing IP right it started working.

  Also note approach default host IP and debug also did not work. This is FYI.

  Thank you.

• cannot find configuration debug «backberry t air application»

  Hello

  I use Flex 4 plugin for eclipse. I tried to create my first application by following the steps in the guide started it. After writing a code I tried to adjust the cnfiguration of Debug as mentioned in the guide, however, I discovered that I don't have Blackberry applications of compressed Air as a type of cnfiguration of debugging in the Debug Configuration screen.

  When installing Backberry t Air SDK, I found following a non-fatal error in logs

  Custom action: com.zerog.ia.customcode.util.fileutils.CopyFile
  Status: ERROR
  Additional notes: ERROR - class com.zerog.ia.customcode.util.fileutils.CopyFile NonfatalInstallException C:\Program Files\Adobe\Adobe Flash Builder 4 Plug-in\sdks\... \dropins\blackberry-Tablet-SDK.Link (the system cannot find the path specified)

  Thank you

  OMKAR

  From this thread:

  http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-Air/installation-of-Tablet-SDK-finish...

  And this thread:

  http://supportforums.BlackBerry.com/T5/Tablet-OS-SDK-for-Adobe-AIR/Flash-Builder-4-does-not-have-the...

  This was the fix:

  «In the folder Tablet OS SDK installed, there is a subfolder 'Eclipse', inside, there is a file called "blackberry-tablet - sdk.link".» Copy this file into your Eclipse 3.6.1 "dropins" folder, restart your Eclipse IDE, you should see the PlayBook Tablet OS SDK in your launch configuration. "

• Why not be able to display boxes of the IP and the password in the configuration of run/debug in Flash builder

  I'm trying to get the HelloWorld application to work, but I can't find the IP address and the option of setting the password for the simulator of tablet in the run/debug configuration. It should be in run/debug configurations, but it's not.

  I already have the Simulator works and correctly installed the Playbook SDK (link to version 2.5 SDK and Flash Builder). I have no error in compilation (QNX namespaces are used), I think that the installation has been correctly executed.

  Please let us know if anyone has the idea to solve this problem.

  Please see below the screenshot associated to above posted the question:

  

  Sometimes last discussions stressed that some dialog size is bad, and if you resize, you will see where the password field is.  Is that what you face here?

• debugging running directly executable

  Is there a reason you cannot run the executable for debugging a CVI application directly, version without the IDE running?

  How about if the CVI IDE runs, but he has another project selected as active project?

  I see the circumstance where if I run the application in the IDE debug configuration, it works as expected.  If I run the same executable, but directly by double-clicking the name of the executable for debugging, then the executable file that closes unexpectedly after having worked for a few minutes.

  Thank you

  Menchar

  This is the reason for the behavior I saw.

  Another developer has misused the Win32 SDK FormatMessage function.  It was the concatenation of its own channel on the system error message string without telling the function to allocate room in the message string (which you can easily do - service designed to allow this, if you tell him).

  Thus, on the basis of an error code, FormatMessage returned a pointer to a string that is just large enough to hold the message that it was formatted in.  When the calling code added to this chain, it was overwhelming who knows what into memory - buffer overflow.   I had also disabled the installation of Win XP DEP (Data Execution Prevention).   If passing went unnoticed and in debugging autonomous image was crush something essential as this would cause program terminate without a popup of exception or a system recording event!

  Somehow when the same image was running of the CVI, the heap has been get allocated / handled differently as the buffer overrun caused no damage.

  The CVI debug versions can watch for overruns buffer for user-defined matrices, but obviously cannot do that when you invaded a buffer allocated to the system.

  The world is so logical, after all :-)

  Menchar

• Debug vs out - why should I use one over the other

  Hi all

  I have always understood that in the preparation for the final release software and delivery that this should be done using the Release configuration. It's the way that other companies offer their software, so it just makes intuitive sense to me. However, I recently came across a project developed and published all of their modules in software using the build configuration Debug, and reasoning that gave me was that it makes debugging easier when troubleshooting problems after release. Now we intend to use this software for a new project, and I don't know that I am ready to support this reasoning. Beyond reason "because I said!", there are several reasons why I think this isn't a good idea:

  1. it is slower to run debugging code. but for what we use for (drivers and utilities for the most part) it is negligible.

  2. There is a potential for malfunctions due to debug code that results in errors or be out of date.

  3. There could be differences between the debug and release configurations (no not the least of which is the use of the _CVI_DEBUG_ macro to include the additional debugging code).

  4 if I remember correctly, to debug properly, the source code must also be available; and for me, this is a big fat no-no giant for a production environment.

  So, beyond reasons I quoted above, and assuming that they are all valid, can anyone provide additional reasons for or against this practice? Any comments would be extremely helpful! Thank you!

  -Jack

  Hello Jack,.

  It is indeed surprising that the company has decided to ship built in the debug configuration.

  Here are some more reasons other debug versions offering isn't a good practice:

  1. The Debug versions are slower due to lack of optimizations.
     1. The compiler tends to optimize the code in release builds, to make it more faster and perform better on specific platforms (it can also slightly obfuscate the code).
     2. The useless instructions or data are deleted in release builds.
  2. Less memory is used by the source code when running in release builds.
  3. The Debug versions may contain debug information stored in the executable/binary file itself. This debugging information is stores the data on the source code, the names of variables and others. This allows not only the code to run more slowly, but it also exposes internal information (this can probably still provide proprietary information to your users).
  4. Debug builds usually initialize variables and data with 0. This means that programmatic errors are usually hidden by the present.
  5. Debug builds are usually (much) bigger than the trade and slower versions.

  There are other alternatives to shipped debugging binary and perform diagnostics on them:

  1. Newspapers: The embedded application can produce newspapers in the special files/folders or the Windows event log. You can also ask your customers to allow facilities to record special in your application, if the problem can be reproduced consistently and provide the log output for you, for further analysis.
  2. Dumps can be analyzed using the same map files for release builds. Crash address usually refers to a location near a function entry point, you can track your mapping files. When you build your binary files in release configuration, the compiler can also generate the map files that you need.

  In addition, as ebalci said, you must make sure that test you your Release version carefully, before shipping.

  Kind regards

  -Johannes

• error - how to debug?

  Hello

  I am new to the blackberry development. I am working on an app for BB10. my host is w8 64bits. I get this error when I try to compile my application:

  do: [Device-Debug] error 2

  not the error report more descriptive that I've ever seen.   can someone point me in the right direction to understand what I did wrong?

  Here the output of the console:

  10:40:21 * incremental Build of the unit for project Geolog debug configuration *.
  make - j4 device-Debug
  do .//translations - C f Makefile update
  make [1]: Entering directory "C: / users/abib/momentics-space work/Geolog/translations"
  C:, bbndk, host_10_2_0_15, win32 / x 86/usr/bin/lupdate Geolog.pro
  Update 'Geolog.ts '...
  Found 12 source text (s) (0 new and 12 already existing)
  make [1]: leaving directory ' C: / users/abib/momentics-space work/Geolog/translations.
  do .//translations f - C release of Makefile
  make [1]: Entering directory "C: / users/abib/momentics-space work/Geolog/translations"
  C:, bbndk, host_10_2_0_15, win32 / x 86/usr/bin/lrelease Geolog.pro
  Update 'C:/Users/abib/momentics-workspace/Geolog/translations/Geolog.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  Ignored for 12 untranslated source text (s)
  make [1]: leaving directory ' C: / users/abib/momentics-space work/Geolog/translations.
  make - c / arm f Makefile debugging
  make [1]: Entering directory "" C: / users/abib/momentics-space work/Geolog/arm ' "
  do f Makefile.Debug
  make [2]: Entering directory "" C: / users/abib/momentics-space work/Geolog/arm ' "
  CQS-Vgcc_ntoarmv7le - c - Wc, - inclure-Wc,o.le-v7-g/.obj/Geolog-Wno psabi - lang-c ++-fstack-protector - fstack-protector-all - mcpu = cortex-a9 - g - Wno-psabi-wall-W-D_REENTRANT-DQT_NO_IMPORT_QT47_QML-DQ_OS_BLACKBERRY-DQT_DECLARATIVE_DEBUG-DQT_DECLARATIVE_LIB-DQT_NETWORK_LIB-DQT_CORE_LIB-DQT_SHARED - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-CQS -... /... / Geolog - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtCore - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtNetwork - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/include/qt4/QtDeclarative - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/inclure/qt4-Io.le-v7-g/.moc - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/include - Ic: / bbndk/target_10_2_0_1155/qnx6/usr/include/freetype2 - i. o o.le-v7-g/.obj/moc_Gab.o o.le-v7-g/.moc/moc_ GAB.cpp
  o.Le - V7 - g. MOC/moc_Gab.cpp: in member function ' virtual int Gab::qt_metacall (QMetaObject::Call, int, void *) ':
  o.Le - V7 - g. MOC / moc_Gab.cpp:132:63: error: 'isFAvorite' was not declared in this scope
  CC: C:/bbndk/host_10_2_0_15/win32/x86/usr/lib/gcc/arm-unknown-nto-qnx8.0.0eabi/4.6.3/cc1plus caught signal 1
  make [2]: * [o.le-v7-g/.obj/moc_Gab.o] error 1
  make [2]: leaving directory ' C: / users/abib/momentics-space work/Geolog/arm.
  make [1]: * [debug] error 2
  make [1]: leaving directory ' C: / users/abib/momentics-space work/Geolog/arm.
  make: * [Device-Debug] error 2

  10:40:23 completed Build (a 2s.136ms)

  debugging is used for enforcement issues. build problems cannot be debugged.

  look a few lines, it tells you what the question is:
  error: 'isFAvorite' was not declared in this scope

  Maybe you typed? A big seems strange.

• Deploy the debugging token: no route to host

  I'm using Linux, deploying a token of debugging on a BlackBerry Z10.

  The mode of development, the dev what IP posted on the parameters is 169.254.1.1

  I use the following command: blackberry - deploy - installDebugToken debugtoken.bar - device 169.254.1.1 - password

  And I have the following output:

  Error: Unable to connect: no route to host. Check the settings of IP address for the target. Try to ping the target.

  I can't ping the device from the device using a 169.254.x.x network, unfortunately I am using a 192.168.1.x network.

  I have no firewall, no VPN and the unit is plugged in USB.

  169.254 network cannot be changed on the unit.

  I tried to force my Linux network config, so that I have the following text:

  # ifconfig

  eth1 Link encap HWaddr 00:10:18:31:68:60
  INET addr:169.254.1.2 Bcast:169.254.255.255 mask: 255.255.0.0
  ADR inet6: fe80::210:18ff:fe31:6860 / 64 Scope: link
  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1
  Fall of RX packets: 182264 errors: 0:0 overruns: 0 frame: 0
  Dropped packets: 106368 TX errors: 0:0 overruns: 0 carrier: 0
  collisions: 0 txqueuelen:1000
  RX bytes: 190168290 (190.1 MB) TX bytes: 21806096 (21.8 MB)
  Interruption: 18

  But still, I can't ping the device...

  What did I miss?

  It seems that the device is properly connected to your computer, and networking has been correctly configured. However, the messages that you have found, and the lack of support of ping suggests there is still a network problem prevents you from reaching the unit.

  Did you set it to 'Storage and access' mode 'Windows '? "Windows" mode is RNDIS, which works perfectly and 'Mac' mode (and perhaps her detected) are ECM and has some problems with some linux configurations.

  You can reach the exit of "route ip get 169.254.1.1"? For my part, I see

  169.254.1.1 dev usb0 CBC 169.254.1.2
  cache

  Your network (192.168. *) should not affect your debug configuration, unless your network is a 169.254. * network.

• Can not build waterfalls sample application: can not find the qmake configuration file

  When you try to build a sample application stunts for debugging on the PlayBook, I have some errors in the output.

  I am running Windows 7 (64 bit) using the QNX Momentics IDE.

  Here is the result:

  ----------------------------------------------------------------

  Build the unit for project HelloCascades debug configuration *.

  make the device debugging
  C:/SDK/BB10/host/win32/x86\usr\bin\qmake-spec unsupported\blackberry armv7le-g ++ o arm\Makefile device += HelloCascades.pro CONFIG
  WARNING: Did not find:... / SRC/.h
  WARNING: Did not find:... / SRC/.h
  X-unsupported\blackberry-C:/SDK/BB10/host/win32/x86\usr\bin\qmake-spec 86-g ++ o x86\Makefile simulator += HelloCascades.pro CONFIG
  WARNING: Did not find:... / SRC/.h
  WARNING: Did not find:... / SRC/.h
  make - C. / translations f Makefile update release
  make [1]: Entering directory "C: / SDK/BB10/Apps/translations
  C:/SDK/BB10/host/win32 / x 86/usr/bin/lupdate HelloCascades.pro
  Update 'HelloCascades_en_GB.ts '...
  Found 0 text (s) source (0 new and 0 already existing)
  Update 'HelloCascades_fr.ts '...
  Found 0 text (s) source (0 new and 0 already existing)
  Update 'HelloCascades_it.ts '...
  Found 0 text (s) source (0 new and 0 already existing)
  Update 'HelloCascades_de.ts '...
  Found 0 text (s) source (0 new and 0 already existing)
  Update 'HelloCascades_es.ts '...
  Found 0 text (s) source (0 new and 0 already existing)
  Update 'HelloCascades.ts '...
  Found 0 text (s) source (0 new and 0 already existing)
  C:/SDK/BB10/host/win32 / x 86/usr/bin/lrelease HelloCascades.pro
  Not found in directory name racineLe qmake configuration is not valid.
  Update 'C:/SDKs/BB10/Apps/translations/HelloCascades_en_GB.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  Update 'C:/SDKs/BB10/Apps/translations/HelloCascades_fr.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  Update 'C:/SDKs/BB10/Apps/translations/HelloCascades_it.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  Update 'C:/SDKs/BB10/Apps/translations/HelloCascades_de.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  Update 'C:/SDKs/BB10/Apps/translations/HelloCascades_es.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  Update 'C:/SDKs/BB10/Apps/translations/HelloCascades.qm '...
  Generated translation (s) 0 (0 finished and unfinished 0)
  make [1]: leaving directory ' C: / SDK/BB10/Apps/translations.
  make - c / arm f Makefile debugging
  make [1]: Entering directory "" C: / SDK/BB10/Apps/arm ' "
  do f Makefile.Debug
  make [2]: Entering directory "" C: / SDK/BB10/Apps/arm ' "
  Not find qmake configuration not found directoryCould extended fichierExemple of use OS qmake configuration before you define MAKEFILE_GENERATOR/usr/bin/sh: C:/Users/ROSSL~1/AppData/Local/Temp/make4028-1.sh: no such file or directory
  make [2]: * [o.le - v7-g/HelloCascades] error 127
  make [2]: leaving directory ' C: / SDK/BB10/Apps/arm.
  make [1]: * [debug] error 2
  make [1]: leaving directory ' C: / SDK/BB10/Apps/arm.
  make: * [Device-Debug] error 2

  Build completed *.

  I have bolded the output where I think the problem might be involved.  Is there a problem with the Makefile, or is it a directory I'm missing, or anything else?  I can't see why there is an error while compling.

  Thanks for any help.

  I have the same warnings qmake... is not found . But finally, after that I could successfully implement the objective of the Simulator, the sample application running, even with this qmake warnings.

• Creating a new build configuration

  wants to create a new configuration in Momentics in this compiles differently my app (it will pass a few macros to the compiler C preprocessor when my project is built).

  Let's say I want to base it on the release device, but I want to call device-release-test instead. I can see how to do this step through the IDE already: (project-> Build Configurations-> Manage)

  This will (I assume) build my project on top of the arm/o-le.v7/ directory. What I want, is to have the project built in a new location, so that I can ensure that my binary output never get confused upward.

  I want this configuration rather to be built under the arm-test /o - the .v7 / directory. I believe that this should be possible because the 'Device-profile' configuration made something similar, with builds end up under the arm-p.

  My question is, how is the build in momentics configuration (stored in the .cproject configuration file) specifies this change? I can see the configuraiton of 'Device-profile' in the directory .cproject - but there is no reference to a 'arm-p' directory, and there is nothing in the file PRO of my app which gives an indication of a configuration of 'profile '.

  I grep has my entire code base and I don't see how to do it - but it must be possible. What I'm missing here?

  I figured out how to do this, in case anyone else is interested. The key is to understand that the compilation life cycle begins with the brand and not qmake / myapp.pro I first thought.

  By default, a Makefile waterfalls looks like:

  QMAKE_TARGET  =  myapp
  PROJECT_DIR   := $(dir $(word $(words $(MAKEFILE_LIST)),$(MAKEFILE_LIST)))
  I18N_DIR      := $(PROJECT_DIR)/translations
  
  include mk/cs-base.mk
  

  The cs - base.mk (found in your NDK) contains everything you need to understand how the process works. In cs - base.mk you can see the built-in rules for unit-Debug, device-liberation, Simulator-Debug configurations. These are hard-coded in the build system.

  You do not want to change cs - base.mk to add your own configurations, to fix this add the following lines at the end of the Makefile in the root of your application:

  QMAKE_TARGET  = myapp
  PROJECT_DIR   := $(dir $(word $(words $(MAKEFILE_LIST)),$(MAKEFILE_LIST)))
  I18N_DIR      := $(PROJECT_DIR)/translations
  
  include mk/cs-base.mk
  
  # add the following:
  arm-test/Makefile: $(QMAKE_TARGET).pro
  
  Device-Test-Release:
     $(info ***** This is my custom make target ***** )
     @mkdir -p arm-test
     cd arm-test && $(QMAKE) -spec blackberry-armv7le-qcc ../$(QMAKE_TARGET).pro CONFIG+=release CONFIG+=device CONFIG+=test
     $(MAKE) -C ./arm-test -f Makefile release
  

  I wasn't the most appropriate copy rules of cs - base.mk and defined my own rule for the configuration of device-Test-version. The foregoing rules follow these steps:

  1. Creates the arm-test directory
  2. Adds 'test' to the variable CONFIG - this will be available in my PRO account

  Now, you must create a new Configuration of build in the momentics IDE.

  1. Right click on your project in the project (myapp) Explorer. From the context menu, select:
  2. -> Manage the Build Configurations

  In the dialog box handle Configurations, click 'new '.... "and create a new configuration called 'Device-Test-Release' (or whatever you wish to call your. Make sure that copy you the settings from a Configuration of 'existing '. Choose the most appropriate for your scenario. In my case, I started my new configuration of generation on 'Device-Release.

  At this stage, you select the new build configuration when you build your project:

  1. Right click on your project in the Project Explorer
  2. Build - Configuraitons-> current value
  3. Select the new "device-Test-version" configuration.
  4. Build!

  However, you will find that different nothing happens. This is because the device-Test-version is based on device-release, so exactly the same thing happens when build you. Therefore, change the device-Test-version so that our custom in our makefile rule is called, instead of the default peripheral release target

  Bring up the project properties:

  1. Right click on your project in the Project Explorer
  2. Select Properties
  3. Goto the tab generating C/C++
  4. Select Device-Test-version in the Configuration drop-down list
  5. The behavior of Goto tab
  6. There is two-text fields ('Generation on resource save' and 'Building')
  7. Change the textfields that say "Device-liberation" for "Device-Test-Release.
  8. Click on apply

  The procedure above "links" your configuraiton of build in the IDE, with the brand target in your Makefile. Now, when you build your project (in the configuration of the device-version-Test), it will be integrated in the arm-test / directory

  There are still two other things you need to do if:

  Edit your file of bar - descriptor.xml and add a new configuration, based on what you see for release device. Just copy the article release device that is already defined, as follows:

  
    Qnx/Cascades
    armle-v7
    myapp
  
  

  You must make sure that the arm-test folder and of course change

  Once you have done this, you can finally edit the myapp.pro file and specify some custom in there rules. I didn't add the following rule:

  # put this in the myapp.pro file
  
  test {
    DEFINES += TEST_BUILD_WHOOP
  }
  

  Don't forget the ' test of += CONFIG "that we put into the Makefile project? In the PRO file above, we leverage this by creating a test rule {}, which applies only when we build the configuration of device-Test-version. Whenever the rule of test runs, we can add a TEST_BUILD_WHOOP preprocessor definition. Now every time our source files are compiled (in the test configuration), the TEST_BUILD_WHOOP macro is defined, and we can put custom code that gets compiled only when we test.

  for example in your myapp.cpp file:

  #ifdef TEST_BUILD_WHOOP
  
  /* whoohoo! building for test */
  
  #endif