User forums > Using Code::Blocks

How to set up C::B for Android NDK compiler?

<< < (3/9) > >>

amarty:

--- Quote from: dmoore on November 15, 2012, 04:14:28 pm ---We need to do something about that error message.

--- End quote ---
It's a good idea.
First, it is not quite how works the "Autodetect" button - it simply reports that nothing is found and fills "Compiler install dir" with "C:\Program Files (x86)\GNUARM" value.
Next, The executable are under bin subdirectory of taken directory, but I can't understand, is path incorrect or something wrong then compiler tryed to run.
Third, what is strange restriction when binaries must be placed under "bin" subdirectory? I think, much better to point exact to directory which contains compiler executables.
Fourth, near all fields, near [...] button will be cool if one more button be placed, [AutoLocate] - pressing on it C::B looks for files in "compiler/install/dir/bin" with mack "*gcc", "*g++", "*ar", "*gdb" etc.

dmoore:

--- Quote from: amarty on November 15, 2012, 09:04:18 pm ---Next, The executable are under bin subdirectory of taken directory, but I can't understand, is path incorrect or something wrong then compiler tryed to run.

--- End quote ---

Related: because the IsValid() check returns false, we get this "invalid" compiler message instead of attempting to run the toolchain command. It's bizarre that the check is only based on the C toolchain command and apparently not anything else.

@op: did you install the NDK while C::B is open? Sometimes I have found you need to close and reopen C::B for the environment to pick things up correctly. (This one is probably a stretch)

amarty:

--- Quote from: MortenMacFly on November 15, 2012, 09:01:25 pm ---You can use the cb_share_config tool, export the compiler settings in question and attach it to a post here, besides you PATH environment variable, and again the exact path where you installed your compiler into.

--- End quote ---
NDK root: D:\android-ndk-r8b
Binaries are in: D:\android-ndk-r8b\toolchains\arm-linux-androideabi-4.4.3\prebuilt\windows\bin
Path : c:\arc;C:\Program Files\ImageMagick-6.7.8-Q16;C:\Program Files (x86)PHP;C:Program Files (x86)IntelComposer XE 2011 SP1\redist\ia32\tbb\vc10;C:\Program Files (x86)IntelComposer XE 2011 SP1\redist\intel64\tbb\vc10;C:\Program Files (x86)IntelComposer XE 2011 SP1\redist\intel64\ipp;C:\Program Files (x86)IntelComposer XE 2011 SP1\redist\ia32\ipp;C:\Program Files (x86)IntelComposer XE 2011 SP1\redist\intel64\mkl;C:\Program Files (x86)IntelComposer XE 2011 SP1\redist\ia32\mkl;C:\Program Files (x86)Common Files\Microsoft Shared\VSA\10.0\VsaEnv;C:\Program Files (x86)Common Files\Intel\Shared Libraries\redist\intel64\mpirt;C:\Program Files (x86)Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\Program Files (x86)Common Files\Intel\Shared Libraries\redist\ia32\mpirt;C:\Program Files (x86)Common Files\Intel\Shared Libraries\redist\ia32\compiler;C:\Program Files (x86)Common Files\Intel\Shared Libraries\redist\intel64\compiler;C:\Program Files (x86)Common Files\Intel\Shared Libraries\redist\ia32\compiler;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;f:\usr\bin;c:\Program Files (x86)Microsoft SQL Server\90\Tools\binn\;C:\Program Files\7-Zip;C:\Program Files (x86)Microsoft Visual Studio 8\Team Tools\Performance Tools;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\Program Files (x86)Graphviz 2.28\bin;C:\Program Files (x86)Javajre7bin;C:Program Files (x86)Javajre7binclient;D:apache-antbin;D:android-sdkstools;D:MinGWbin;D:MinGWmsys1.0bin;D:necessitasAndroidQt482armeabibin;D:necessitasapache-ant-1.8.4bin;D:CMakebin;C:Program Files (x86)Subversionbin;C:Program Files\TortoiseSVN\bin




--- Quote from: MortenMacFly on November 15, 2012, 09:01:25 pm ---BTW:  I didn't even know there is a GCC for android... interesting... :-)

--- End quote ---
Android Native Development Kit - NDK

MortenMacFly:

--- Quote from: amarty on November 15, 2012, 09:04:18 pm ---First, it is not quite how works the "Autodetect" button - it simply reports that nothing is found and fills "Compiler install dir" with "C:\Program Files (x86)\GNUARM" value.

--- End quote ---
This is by design. The folder is the default folder, where the compiler usually is installed, if you run its installer.


--- Quote from: amarty on November 15, 2012, 09:04:18 pm ---Next, The executable are under bin subdirectory of taken directory, but I can't understand, is path incorrect or something wrong then compiler tryed to run.

--- End quote ---
Well you can - what I told you is true: If you see this message, CodeBlocks cannot find the compiler computed by [list of path's] + compiler executable.


--- Quote from: amarty on November 15, 2012, 09:04:18 pm ---Third, what is strange restriction when binaries must be placed under "bin" subdirectory? I think, much better to point exact to directory which contains compiler executables.

--- End quote ---
Again, this is by design. Most compilers are setup in a way that they have a root folder, which has at least the sub-folders "bin" for the tool chain executables, an"include" folder for its includes and a "lib" folder for libraries. So having to setup the root path is just convenient to find all the rest. Otherwise it will become so complicated that out forum will be flooded with messages "I don't get the compiler to run" - trust me.


--- Quote from: amarty on November 15, 2012, 09:04:18 pm ---Fourth, near all fields, near [...] button will be cool if one more button be placed, [AutoLocate] - pressing on it C::B looks for files in "compiler/install/dir/bin" with mack "*gcc", "*g++", "*ar", "*gdb" etc.

--- End quote ---
Nope. We also support compilers like MSVC where you don't have such executables and even non c/c++ compiler (take Fortran, for example). Also, we support compilers that do not have such a standard folder structure. So your suggestion will break all these cases. the way it is now works for all of them and more.[/list]

amarty:

--- Quote from: dmoore on November 15, 2012, 09:19:27 pm ---@op: did you install the NDK while C::B is open? Sometimes I have found you need to close and reopen C::B for the environment to pick things up correctly. (This one is probably a stretch)

--- End quote ---

No, NDK installed some time ago, and some time I use Eclipse for development, but C::B is more nice IDE (I had the experience of using it before), and now I try to configure C::B for NDK.

Navigation

[0] Message Index

[#] Next page

[*] Previous page