Quirk of QCC compilation.

Similar Questions

• Shared libraries

  I'm having some trouble with making a shared library or libraries in general.

  Question #1

  I create a shared library code, header, etc. Build the project and... nothing. According to my console:

  Build error
  Generated resource conflict:
  two resources of the same name: /sharedLib/Device-Debug/src/codeFileInSharedLib.o
  generated by different tools
  tool1: QCC Compiler
  tool2: QCC Compiler
  

  I can't find anything on it, but it gives me headaches and refuses to compile.

  This opens to question #2, in fact, I managed to get the project to compile (when she was smaller and more basic) but he bumped to another question when I tried to connect to a project:

  cannot find -lsharedLib
  

  Now based on what I got from the beta forums:

  elenalaskavaia:
  
  Depends what project type you have, normally you don't want to link again .o file, you should create a library and link with library. You can create a static library project called myboost, copy you source there.
  If this a managed project it will be all set you just have to build it. It will produce libmyboost.a file
  
  In the project that using it you have to specify few things - that a) you want to link to that library  b) where to find it c) where to find headers for this library d) if you want you can specify project dependency, so if you change library you binary project will be automatically recompiled
  
  Docs for managed projects set-up
  
  --------------------------------
  
  For manage projects (both main and library are managed projects).
  
  Main project is aaa and library is bbb.
  
  * Specify library and library path in linker
  In aaa project properties->C/C++ Build->Settings->QCC Linker->Libraries
  
  - Select "All configurations" in Configuration drop down at the top of the
  window
  - In library path add ${workspace_loc:/bbb}/${ConfigName} (Click add icon)
  (variable with $ are verbatim, bbb is the project name which changes)
  
  - In libraries, click Add and add you library name, i.e. bbb
  
  * Specify includes
  - Switch to Qcc Compiler->Preprocessor on the left
  
  - Add include folder ${workspace_loc:/bbb/src} (assuming public headers for bbb
  library in src folder of bbb project
  In aaa project properties->C/C++ General->Paths and Symbols->Referebces tab
  
  * Specify dependency
  - In configurations select your active configuration (on top)
  
  - Expand bbb project and select matching configuration
  
  - Unfortunately you have to repeat it for all configurations you use (Select
  Configuration on top, then check reference to matching configuration in bbb
  project)
  Press Apply and close the dialog
  

  I was able to get the project to post a link, but this seems a little more finicky (as if I change a library in General "C/C++" project ownership, it erases the libraries located in ' C/C++ Build'.

  Finally, the question I have not met yet, number #3:

  How truly I create an application that uses a shared library, because shared libraries are not supported (in the direction of load a single library and everyone can access). The Release version (which creates a BAR) will add him or this library I need to do something more?

  So after all that, advice or solutions?

  I guess I should do the same for a static library?

  * facepalm * okay, nevermind. I didn't know that I had 2 files of source code with the same name. Question #1 and #2 set. I'll leave the thread open if someone knows the answer to the #3 question.

• Accidents of application only in Release version

  Hi all

  I have a mysterious problem that I don't know how to diagnose.

  I use sqlite (fusion of the file i.e. all sqlite3 in a single file) with my application written in NDK 2.0.

  I use it to dynamically create a database named "data / dan.db".  When I use the token of debugging for the debug version, everything works.  However, when I use the export release generated files, the application simply crashes at launch.  In fact, the problem seems to be the sqlite3_open() command.  If I comment on this possibility, the application load.  As soon as I put it in, the application crashes.

  I don't know why my app works very well with the build for the debugging token, but not as a release.

  Any help will be greatly appreciated.

  Oh... Once I got the same problem, but my app did not start at all. I managed to "fix" this by disabling the "Pavilion of Position executable independent" in the compiler and linker.

  You can compare all the indicators you use to Debug and Release build by going to the properties of the project->-generation C / C++-> settings and you are looking to QCC compiler/assembler/Linker when choosing the different Build Types in the Configuration field especially this kind of things.

• Problem using the Qt library in static library

  I created a static library with SDK 10.1 10.2 Momentics. Any time I get the qt classes, the compiler complains that it cannot find a file any.

  for example:

  #include

  the error is:

  The path location type Resource Description
  Fatal error: QtCore/qchar.h: no such file or directory MyStaticLibrary line 45, external location: /Applications/Momentics.app/target_10_1_0_4828/qnx6/usr/include/qt4/QtCore/qstring.h C/C++ problem

  Help, please.

  I have a simular problem solved by adding a variable include

  ${QNX_TARGET} / usr/include/qt4 in

  Project / Properties / C/C++ Build / Settings /Tool settings /QCC compiler / preprocessor / Include directories (- I).

• Cascades Zygote and linking with static libraries

  Using the SDK Gold version 10.0.9.2318 to build a project that uses the static libraries. Libraries have been created using the new BlackBerry Project Wizard. Applications generate and perform well in all generation except release device configurations. Application files build very well, but when the time comes to bind the build fails with:

  libGeoLib.a(UTMUPS.o): relocation R_ARM_THM_MOVW_ABS_NC against `__stack_chk_guard' can not be used when making a shared object; recompile with -fPIC
  

  I assumed that the build system attempts to link all libraries in a large library shared but fails because the object files used to build the archives are not build properly (without the option - FPIC).

  Is it possible to exclude static libraries of the generation of object of shared zygote? Or y at - he shared a way to get the archives of the library built with required options so that they can be held to the object of the zygote?

  I think I solved this problem.

  In Momentics, right click on the static library project, select Properties. Building Goto C/C++, settings. Create device-output configuration. In the tool settings tab select QCC Compiler Options. Add the - fpic to QCC Options.

  In the PRO application's project file, you may need to go back to the old way of defining library search path:

  device {
      CONFIG(release, debug|release) {
          DESTDIR = o.le-v7
          LIBS +=  -L../../GeoLib/Device-Release -L../../shape/Device-Release
      }
      CONFIG(debug, debug|release) {
          DESTDIR = o.le-v7-g
          LIBS +=  -L../../GeoLib/Device-Debug -L../../shape/Device-Debug
      }
  }
  
  simulator {
      CONFIG(release, debug|release) {
          DESTDIR = o
          LIBS += -L../../GeoLib/Simulator-Debug -L../../shape/Simulator-Debug
      }
      CONFIG(debug, debug|release) {
          DESTDIR = o-g
          LIBS += -L../../GeoLib/Simulator-Debug -L../../shape/Simulator-Debug
      }
  }
  

• BB10 Error gold under construction

  I just downloaded and installed the BB10 Gold.

  Pulled up and tried to make a construction on an existing project that I had any problem with before.  I get a compilation error:

  Internal generator is used to build *.
  QCC o src\main.o... \src\main.c-V4.4.2, gcc_ntoarmv7le-w1 - IC: / BB_SDK/target/qnx6/usr/include/freetype2 - IC: / BB_SDK/target/qnx6 /... / goal-override/usr/include - D_FORTIFY_SOURCE = 2 - c - g - fstack-protector-strong O0
  Cc1: error: unrecognized command line option '- fstack - protector-fort ".
  CC: C:/BB_SDK/host/win32/x86/usr/lib/gcc/arm-unknown-nto-qnx6.5.0eabi/4.4.2/cc1 caught signal 1
  Build error has occurred, build is stopped
  Time consumed: 4483 ms.

  I don't know what to do with it.  There is obviously some sort of command line option that is not fair, but I have no experience in changing these kinds of things.

  Any suggestions?

  Well, my solution is (I don't know what are the other consequences it can have):

  (1) go to the project properties (I assume you are using QNX Momentics IDE)

  (2) generation C/C++

  (3) settings-> settings-> control out of QCC compiler tool-> uncheck "improved security (- fstack - protector-strong)" option

  (4) rebuild

  Works for me.

• Is this a bug or a feature?

  ActionScript...

  String.a = 3;

  Compiler reports an error.

  ActionScript...

  As = String;

  As.a = 3;

  trace (As.a) / / output: 3

  We see what VM Flash can set the built-in class attribute, but compiler prohibits who. Is this a bug or a feature of machine virtual Flash?

  Thank you!

  As kglad, these two statements will not compile:

  String.a = 3;
  As = String;

  The first, because you can't directly add properties to a final class and the second because "as" is a key word.

  That said, there's a quirk (in the compiler used by CS3 - CS4 not know) that allows you to add indirectly of the properties to the class String (and others). for example

  var Ref: * = String;
  REF.a = 3;
  Ref.FCC = function(... args)
  {
  return this.fromCharCode.apply (this, args)
  }
  trace (Ref.a)
  trace ((String en tant qu'objet) .to)
  trace ((String_comme_Object).fcc (33,34,35))

  However, I find no reason to do something like this and absolutely no value to use something that is not available in future versions.

• Compiler issues C++ Momentics.

  Hi all here!

  I started playing with the development of BlackBerry, I installed 2.1 Momentics and BB 10.3 Windows SDK 8.1, the Simulator and everything seems to work very well.

  However, I would like to ask a question about the C++ compiler that uses Monetics IDE:

  a. I see that the default build tools is a "QCC QNX. What is a custom version of GCC?

  (b) I tried to use certain features of the C ++ 11 but had compilation errors. Is there a place on the IDE where should I put the "" - Wc, - std = gnu ++ 0 x ' and I'll be OK or not? " C ++ 11 soustenans is at all?

  c. What is the difference between "QNX QCC" (which seems to be the default) and "Multi - toolchain QNX? Which should I use?

  Many thanks for any help on this.

  Welcome on the support forums.

  no idea on the two others, but c ++ 11 is not supported.

• qmake configuration so that x 86 compilation is used

  Hello everyone.  I had trouble with the IDE from QNX reports 'out of memory', which is a mistake that I know well since I use Ecplise frequently.

  I would use Makefiles to compiling a project BB10 NDK.  I used qmake to generate the makefiles and successfully compiled them.  I am a new Blackberry developer and I need to test my code using the Simulator because I do not have a peripheral BB10 alpha and BB10 is not yet available for PlayBook.

  How can I tell qmake to generate the Makefile appropriate to the Simulator?

  In Qt Creator, by the way - blackberry - x 86 - QCC to qmake spec changes the compiler settings used, so that you get x 86 build.

• problem compiling with references to projects

  Hello

  I developed as a framework and I'm trying to bring to BB10.

  I have four static libraries, have references to others.

  I create a project test using the four libraries and checked in the window references my four libraries (QNX IDE: project properties / general ad for C/C++ /Paths symbols / References).

  When I compile I have many ' reference "..." "undefined error. I know that I can change the order of the links, but it is not enough to solve some "circular" linking problems.

  I already had this problem when I compiled the framwork for Android, but in the makefile, I was able to link several times with the same library (example:)

  Project4.a
  Project1.a

  Project3.a
  Project1.a
  Project2.a
  )
  But I can't, or I don't know how I can do it in QNX IDE.

  No idea how I can do to link all my projects properly please?

  Thanks a lot for your help.

  You should put all your libraries to be used by the editor of links here:

  Build properties of the project-> C/C++/QCC Linker-> library-> library (-l)

• Problem with compiling QT application

  Hi people,

  Palybook is in general a nice tab, my wife a QA test lead on our society and she's like to test the new application and material, but after 1.5 hours of research, I look at and test drive android is crashes WOW... real QA. QNX works very well.

  But, I'm a developer, and I have a strange problem with QT env for Simulator playbook.

  I use manual http://wiki.qt-project.org/QNX to build qt for qnx env.

  Any compilation fine and installed in the directory prefix as well.

  Then I prepare simple program ' Hello world ' to test whether anything can build successfully.

  My system is gentoo with kernel 3.2.12

  my project as:

  /home/miha/playbook_simulator_2_0/qt/x86/bin/qmake -project
  
  which qcc
  /home/miha/playbook_simulator_2_0/bbndk-2.0/host/linux/x86/usr/bin/qcc
  
  which make
  /home/miha/playbook_simulator_2_0/bbndk-2.0/host/linux/x86/usr/bin/make
  

  chain of QCC

  qcc -Vgcc_ntox86 -c -fstack-protector -fstack-protector-all -Wno-psabi -O2 -Wall -W -D_REENTRANT -DQ_OS_BLACKBERRY -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I../../x86/mkspecs/unsupported/blackberry-x86-qcc -I. -I../../x86/include/QtCore -I../../x86/include/QtGui -I../../x86/include -I. -I. -I../../../bbndk-2.0/target/qnx6/usr/include -I../../../bbndk-2.0/target/qnx6/usr/include/freetype2 -o main.o main.c
  

  QNX variable:

  QNX_CONFIGURATION=/home/miha/.rim/bbndk
  QNX_TARGET=/home/miha/playbook_simulator_2_0/bbndk-2.0/target/qnx6
  QNX_HOST=/home/miha/playbook_simulator_2_0/bbndk-2.0/host/linux/x86
  

  and have a strange output in the console: (~ 2700 output lines)

  In file included from ../../x86/include/QtCore/qobjectdefs.h:45,                 from ../../x86/include/QtCore/qobject.h:47,                 from ../../x86/include/QtCore/qcoreapplication.h:45,                 from ../../x86/include/QtGui/qapplication.h:45,                 from ../../x86/include/QtGui/QApplication:1,                 from main.c:1:../../x86/include/QtCore/qnamespace.h:54: warning: return type defaults to 'int'../../x86/include/QtCore/qnamespace.h: In function 'QT_MODULE':../../x86/include/QtCore/qnamespace.h:54: error: expected declaration specifiers before 'namespace'../../x86/include/QtCore/qnamespace.h:1799: error: expected declaration specifiers before 'Q_DECLARE_OPERATORS_FOR_FLAGS'../../x86/include/QtCore/qnamespace.h:1820: error: expected declaration specifiers before 'class'../../x86/include/QtCore/qnamespace.h:1875: error: expected declaration specifiers before ';' tokenIn file included from ../../x86/include/QtCore/qobject.h:47,                 from ../../x86/include/QtCore/qcoreapplication.h:45,                 from ../../x86/include/QtGui/qapplication.h:45,                 from ../../x86/include/QtGui/QApplication:1,                 from main.c:1:../../x86/include/QtCore/qobjectdefs.h:51: error: expected declaration specifiers before 'QT_MODULE'../../x86/include/QtCore/qobjectdefs.h:55: error: expected declaration specifiers before 'class'../../x86/include/QtCore/qobjectdefs.h:143: error: expected declaration specifiers before 'template'../../x86/include/QtCore/qobjectdefs.h:146: error: expected declaration specifiers before 'template'../../x86/include/QtCore/qobjectdefs.h:217: error: expected declaration specifiers before 'Q_CORE_EXPORT'
  
  . . . . . . . . . .
  

  Can someone help me with this? or someone knows what is happening and how to fix this strange situation?

  Mike.

  Have you tried to compile it in Qt Creator?

  And did you use Qt download on: http://openbbnews.wordpress.com/2012/03/29/qt-update-2/

  There is no real need to compile by yourself

  SRY, I could not help you directly, cause I use Windows XP to compile for Playbook. The Linux installer does not work with my 32-bit Kubuntu.

  [edit]

  found this:

  http://StackOverflow.com/questions/7512433/error-expected-declaration-specifiers-before-namespace

  [/ Edit]

• Compile and link time?

  Hello BlackBerry devs,

  We are developing a relatively large application composed of nearly 1,500 units of compilation spread over 2 static libraries and the main application. We use WNX Momentics and managed to build. Total hours of recompilation are 40 minutes with a time of 5 minutes on the final application link. Y at - it all the settings people may know who could help in this area?

  We use preincludes in all projects. It seems a PCH file would be beneficial in this case, however, it doesn't seem to be a way to allow this in managed Momentics is based.

  Also, our code base depends on the abbreviated wchar_t (- fshort - wchar). This causes the linker emits a warning (uses 2 bytes wchar_t and yet the result is to use 4 bytes wchar_t; use of wchar_t values among the objects may fail) for each linked object which, with more than 1500 linked object causes a LOT of output and probably slows down the link accumulate these messages. It doesn't seem to be a way to silence this warning because - fshort-wchar allows effectively to its default error status warning.

  Thank you very much

  Stéphane

  Hi Stephane,

  I did not explicitly build settings for the precompiled headers but confirmed that they are supported.  Since they are standard options of GCC, you can add them to the General settings QCC options page.  I'm trying to see if someone has internal settings that I can share.

  On the linker WARNING: changes the ABI - fshort-wchart and makes the code incompatible with the libraries on the system. That's why the linker warns about the incompatibility of the ABI. It isn't a caveat that must be silenced, but if you wish, you can do so using the - Wl,--no-warn-incompatibility.

• When I compile skied lib for blackberry 10, I encountered an error "A7 cannot be used in asm here."

  To draw text in the cascades, I found this article:

  http://supportforums.BlackBerry.com/T5/tkb/articleprintpage/tkb-ID/Cascades@tkb/article-ID/14

  but when I compile the lib skied, I encountered this error, no idea about it, can anyone help?

  QCC o src\opts\SkBlitRow_opts_arm.o... \src\opts\SkBlitRow_opts_arm.cpp-V4.6.3, gcc_ntoarmv7le_cpp-no-w1-shared - IF: / bbdev/bbndk/target_10_0_9_386/qnx6/usr/include/freetype2 - IF: \bbdev\bb10Apps\blackberry-Skia\gpu\include-IF: \bbdev\bb10Apps\blackberry-Skia\include\config-IF: \bbdev\bb10Apps\blackberry-Skia\include\core-IF: \bbdev\bb10Apps\blackberry-Skia\include\effects-IF: \bbdev\bb10Apps\blackberry-Skia\include\gpu-IF: \bbdev\bb10Apps\blackberry-Skia\include\images-IF: \bbdev\bb10Apps\blackberry-Skia\include\utils-IF : \bbdev\bb10Apps\blackberry-Skia\src\core-IF: / bbdev, bbndk, target_10_0_9_386, qnx6 /... / goal-override/usr/include - D_FORTIFY_SOURCE = 2 - Dgrskia_EXPORTS-D_FILE_OFFSET_BITS = 64-D_LARGEFILE64_SOURCE-DSKIA_IMPLEMENTATION = 1 - DGR_IMPLEMENTATION = 1 - DGR_QNX_BUILD = 1 - DUSE_GANESH = 1 - /DDEBUG - c g - fstack-protector-all - fstack-protector - fno-strict-aliasing - fno-rtti - fpic - fvisibility = hidden - mtune = cortex-a9 - mfpu = vfpv3-lang-c ++
  .. \src\opts\SkBlitRow_opts_arm.cpp: function ' void S32A_Opaque_BlitRow32_arm (SkPMColor *, SkPMColor const *, int, U8CPU)':
  .. \src\opts\SkBlitRow_opts_arm.cpp:655:1: error: A7 cannot be used in asm here
  CC: F:/bbdev/bbndk/host_10_0_9_52/win32/x86/usr/lib/gcc/arm-unknown-nto-qnx8.0.0eabi/4.6.3/cc1plus caught signal 1
  Build error has occurred, build is stopped
  Time consumed: 193984 ms.

  I found the solution.  Add the option of compilation of QCC:

  -fomit-frame-pointer

  now I get him skied lib for blackberry 10

• Cross compiling Mono error

  Hello

  I'm trying to compile this version of Mono (https://github.com/roblillack/mono/tree/qnx-2-10-9) for the emulator of BB OS 10

  But I got the error of nex:

  libmonosgen_2_0_la - mini.lo libmonosgen_2_0_la-method-to - ir.lo libmonosgen_2_0_la - decompose.lo libmonosgen_2_0_la-jit - icalls.lo libmonosgen_2_0_la - trace.lo libmonosgen_2_0_la - dominators.lo libmonosgen_2_0_la - cfold.lo libmonosgen_2_0_la - regalloc.lo libmonosgen_2_0_la - helpers.lo libmonosgen_2_0_la - liveness.lo libmonosgen_2_0_la - ssa.lo libmonosgen_2_0_la - abcremoval.lo libmonosgen_2_0_la - ssapre.lo local-libmonosgen_2_0_la - propagation.lo libmonosgen_2_0_la - driver.lo libmonosgen_2_0_la-debug-libmonosgen_2_0_la-linear mini.lo - scan.lo libmonosgen_2_0_la-aot - compile ones libmonosgen_2_0_la-August - runtime.lo libmonosgen_2_0_la - graph.lo libmonosgen_2_0_la - codegen.lo - mini libmonosgen_2_0_la-mini - exceptions.lo mini-libmonosgen_2_0_la - trampolines.lo libmonosgen_2_0_la - declsec.lo libmonosgen_2_0_la - wapihandles.lo libmonosgen_2_0_la-branch - opts.lo libmonosgen_2_0_la-mini-generic - sharing.lo libmonosgen_2_0_la - regalloc2.lo libmonosgen_2_0_la - tasklets.lo simd-libmonosgen_2_0_la - intrinsics.lo libmonosgen_2_0_la - unwind.lo libmonosgen_2_0_la-image - writer.lo libmonosgen_2_0_la - dwarfwriter.lo libmonosgen_2_0_la-mini - gc.lo libmonosgen_2_0_la-debugger - agent.lo libmonosgen_2_0_la-debug - debugger ones libmonosgen_2_0_la - xdebug.lo libmonosgen_2_0_la-mini - x 86 ones libmonosgen_2_0_la-exceptions - x 86 ones libmonosgen_2_0_la-tramp - x 86 ones  libmonosgen_2_0_la-mini - posix.lo... /... mono/Metadata/libmonoruntimesgen.la... /... mono/IO-Layer/libwapi.la... /... mono/utils/libmonoutils.la.-L. /.. / eglib/src - leglib - lm - lsocket
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find lscreen -.
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find - lpng14
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find - lbps
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find - lEGL
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find - lGLESv2
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find-liconv -.
  / Applications/bbndk/host_10_0_6_1/darwin / x 86/usr/bin/ntox86-ld: cannot find - lstdc ++
  collect2: ld returned 1 exit status
  make [4]: * [libmonosgen - 2.0.la] error 1
  make [4]: leaving directory ' / users/developers/Desktop/Monoberry/monosrc/mono/mini.
  make [3]: * [all] error 2

  My build configuration is the following:

  ./autogen.sh--prefix = / users/developers/Desktop/Monoberry/monobuild-with-moonlight = no - with-mcs-docs = no - build = i386-apple - darwin10.7.0 - host = i486-pc-nto-qnx8.0.0--avec-sgen = no - disable-boehm - target = i486-pc-nto - qnx8.0.0

  And my environment variable (bbndk - env.sh):

  # This script sets the environment variables required for this version of NDK
  # to the command line. To use the script, you must 'lighting' in your shell,
  # source bbndk - env.sh
  # If source command is not available "." (dot) command instead
  #

  Environment variables are influential #Some in mono:
  #--> Of done CC C compiler command
  Compiler c# CFLAGS flags--> fact
  # LDFLAGS linker flags, e.g.-L If you have libraries in one
  # Non-standard directory --> fact
  # LIBS libraries to pass to the linker, for example-l --> not the value
  # CPPFLAGS C / C + c++ / Objective C preprocessor flags, e.g. - I if--> fact
  # you have headers in a nonstandard directory
  #--> The fact CXX C++ compiler command
  # Compiler C++ CXXFLAGS flags--> fact
  #--> Compiler assembler common COUNTRY assessments (by default, CC) command fact
  #--> Compiler CCASFLAGS (default CFLAGS) done assembler flags
  C# CPP preprocessor--> fact
  #--> CXXCPP C++ preprocessor
  # XMKMF Path xmkmf, generator of Makefile for X Window System--> not configured

  QNX_TARGET = "/ Applications/bbndk/target_10_0_6_384/qnx6.
  QNX_HOST = "/ Applications/bbndk/host_10_0_6_1/darwin / x 86.
  QNX_CONFIGURATION = "" / Users/developer/library/research in Motion/BlackBerry native SDK ""
  MAKEFLAGS = "'-J' I$ QNX_TARGET/usr/include '"
  DYLD_LIBRARY_PATH = "" $QNX_HOST/usr/lib /: $QNX_TARGET /... / darwin / x 86/usr/lib/qt4/lib: $DYLD_LIBRARY_PATH ""
  Path = "" $QNX_HOST/usr/bin: $PATH ""

  #armv7
  #RANLIB = "${QNX_HOST} / usr/bin/ntoarmv7-ranlib(1)"
  Emulator #x86
  RANLIB(1) = "${QNX_HOST} / usr/bin/ntox86-ranlib(1)"

  #armv7
  #CPP = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntoarmv7le_cpp - E"
  #x86
  CPC = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntox86_cpp - E"

  #armv7
  #CXXCPP = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntoarmv7le_cpp - E"
  #x86
  CXXCPP = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntox86_cpp - E"

  #armv7
  #CC = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntoarmv7le_cpp"
  #x86
  CC = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntox86_cpp"

  #armv7
  #CXX = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntoarmv7le_cpp"
  #x86
  CXX = "${QNX_HOST} / usr/bin/QCC - V4.6.3, gcc_ntox86_cpp"

  #armv7
  #LD = "${QNX_HOST} / usr/bin/ntoarmv7-ld"
  #x86
  LD = "${QNX_HOST} / usr/bin/ntox86-ld"

  CPPFLAGS = "- D__PLAYBOOK__ - D__QNXNTO__.
  "CFLAGS =" g "
  "CXXFLAGS =" g "
  CCAS = $CC
  CCASFLAGS = $CFLAGS

  #armv7
  #LDFLAGS = "-L$ {QNX_TARGET} / armle-v7/lib - L$ {PREFIX} ' / lib - lscreen - lasound - PPR - lm-lpng14 - lbps - lEGL-lGLESv2" "
  #x86
  LDFLAGS = "-L$ {QNX_TARGET} / x 86/lib - L$ {PREFIX} ' / lib - lscreen - lasound - PPR - lm-lpng14 - lbps - lEGL-lGLESv2" "

  export QNX_TARGET QNX_HOST QNX_CONFIGURATION MAKEFLAGS DYLD_LIBRARY_PATH PATH RANLIB(1) CPP CC LD CPP CFLAGS, LDFLAGS CPPFLAGS

  My OS: Mac OS X 10.6.8

  Anyone know what I'm doing wrong? Please, I'm stuck with this problem for a long time!

  change this

  LDFLAGS = "-L$ {QNX_TARGET} / x 86/lib - L$ {PREFIX} ' / lib - lscreen - lasound - PPR - lm-lpng14 - lbps - lEGL-lGLESv2" "

  TO

  LDFLAGS = "-L$ {QNX_TARGET} / x 86/lib - L$ {QNX_TARGET} / x 86/usr/lib - L$ {PREFIX} ' / lib - lscreen - lasound - PPR - lm-lpng14 - lbps - lEGL-lGLESv2" "

• Help: Code does not compile!

  Hello
  Whenever I'm trying to compile my code, I get the following error and I can not understand what the problem is. It started to not once I built a release build and then cleaned the project and tried to build this new (device debugging). I know that in my code has changed, but I can't understand why it won't build. Does anyone have any suggestions?

  **** Build of configuration Device-Debug for project JewelSmuggler Trunk ****
  
  make -j8 Device-Debug
  make -C .//translations -f Makefile update
  make[1]: Entering directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations'
  C:/bbndk/host_10_1_0_132/win32/x86/usr/bin/lupdate JewelSmuggler.pro
  Updating 'JewelSmuggler_de.ts'...
      Found 61 source text(s) (0 new and 61 already existing)
  Updating 'JewelSmuggler_es.ts'...
      Found 61 source text(s) (0 new and 61 already existing)
  Updating 'JewelSmuggler_fr.ts'...
      Found 61 source text(s) (0 new and 61 already existing)
  Updating 'JewelSmuggler_it.ts'...
      Found 61 source text(s) (0 new and 61 already existing)
  Updating 'JewelSmuggler.ts'...
      Found 61 source text(s) (0 new and 61 already existing)
  make[1]: Leaving directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations'
  make -C .//translations -f Makefile release
  make[1]: Entering directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations'
  C:/bbndk/host_10_1_0_132/win32/x86/usr/bin/lrelease JewelSmuggler.pro
  Updating 'C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations/JewelSmuggler_de.qm'...
      Generated 61 translation(s) (61 finished and 0 unfinished)
  Updating 'C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations/JewelSmuggler_es.qm'...
      Generated 61 translation(s) (61 finished and 0 unfinished)
  Updating 'C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations/JewelSmuggler_fr.qm'...
      Generated 61 translation(s) (61 finished and 0 unfinished)
  Updating 'C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations/JewelSmuggler_it.qm'...
      Generated 61 translation(s) (61 finished and 0 unfinished)
  Updating 'C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations/JewelSmuggler.qm'...
      Generated 0 translation(s) (0 finished and 0 unfinished)
      Ignored 61 untranslated source text(s)
  make[1]: Leaving directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/translations'
  make -C ./arm -f Makefile debug
  make[1]: Entering directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/arm'
  c:/bbndk/host_10_1_0_132/win32/x86/usr/bin/qmake.exe -spec c:/bbndk/target_10_1_0_1020/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-qcc CONFIG+=debug_and_release CONFIG+=device -o Makefile ../JewelSmuggler.pro
  make[1]: Leaving directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/arm'
  make[1]: Entering directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/arm'
  make -f Makefile.Debug
  make[2]: Entering directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/arm'
  C:/bbndk/host_10_1_0_132/win32/x86/usr/bin/moc.exe -DQT_NO_IMPORT_QT47_QML -DQ_OS_BLACKBERRY -DQT_DECLARATIVE_DEBUG -DQT_DECLARATIVE_LIB -DQT_CORE_LIB -DQT_SHARED -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-qcc -I../../JewelSmuggler\ Trunk -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/qt4/QtCore -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/qt4/QtDeclarative -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/qt4 -I../src -Io.le-v7-g/.moc -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/freetype2 -I. -D__QNXNTO__ ../src/applicationui.hpp -o o.le-v7-g/.moc/moc_applicationui.cpp
  qcc -Vgcc_ntoarmv7le -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_CORE_LIB -DQT_SHARED -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/share/qt4/mkspecs/blackberry-armv7le-qcc -I../../JewelSmuggler\ Trunk -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/qt4/QtCore -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/qt4/QtDeclarative -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/qt4 -I../src -Io.le-v7-g/.moc -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include -Ic:/bbndk/target_10_1_0_1020/qnx6/usr/include/freetype2 -I. -x c++-header -c ../precompiled.h -o o.le-v7-g/.obj/JewelSmuggler.gch/c++
  cc1plus: fatal error: "-I../../JewelSmuggler Trunk": Invalid argument
  compilation terminated.
  cc: C:/bbndk/host_10_1_0_132/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/JewelSmuggler.gch/c++] Error 1
  make[2]: *** Waiting for unfinished jobs....
  make[2]: Leaving directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/arm'
  make[1]: *** [debug] Error 2
  make[1]: Leaving directory `C:/Users/Rahul/ndk-10.1.0-workspace/JewelSmuggler Trunk/arm'
  make: *** [Device-Debug] Error 2
  

  

  I found the problem here. This problem arose when I put a space in the name of the project. Once I got the space on the compiled for free code number.