User forums > Using Code::Blocks
How to set up C::B for Android NDK compiler?
MortenMacFly:
--- Quote from: amarty on November 15, 2012, 09:39:21 pm ---[...]
--- End quote ---
Your compiler setup is wrong.
Accoridn to your config, you setup a wrong C toolchain executable. If your compiler does not have a GCC, setup the G++ here, too.
I just successfully configured NDK on my PC - so it definitely works with the right setup.
MortenMacFly:
--- Quote from: dmoore on November 15, 2012, 09:19:27 pm ---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.
--- End quote ---
Well the reason for this is that i.e. for MSVC you might only have a C compiler and nothing else. So we don't want to have it overdone. the only exception I can think of is to check for if either the C or the C++ executable is present. But the rest we should leave. Remember that there might even be no "make", no "linker", no "resource compiler".
I think IsValid() should return an enumeration that helps to identify what the error is. Or (maybe a bit ugly) a wxString with the exact error description and wxEmptyString if all is OK.
amarty:
--- Quote from: MortenMacFly on November 15, 2012, 09:43:11 pm ---
--- 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.
--- End quote ---
But compiler exact under that path - I try to copy path, paste it to console, type "\bin\", copy and paste execuatable name, press enter - compiler launches.
--- Quote from: MortenMacFly on November 15, 2012, 09:43:11 pm ---
--- 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]
--- End quote ---
Yes, I understand this. I gave just one example of search mask for C/C++ toolset tools. Also, as I see, in that dialog only C/C++ toolsets can be configured.
amarty:
--- Quote from: MortenMacFly on November 15, 2012, 09:51:01 pm ---I think IsValid() should return an enumeration that helps to identify what the error is. Or (maybe a bit ugly) a wxString with the exact error description and wxEmptyString if all is OK.
--- End quote ---
Yes, I told about something like your proposal too.
amarty:
--- Quote from: MortenMacFly on November 15, 2012, 09:47:02 pm ---
--- Quote from: amarty on November 15, 2012, 09:39:21 pm ---[...]
--- End quote ---
Your compiler setup is wrong.
Accoridn to your config, you setup a wrong C toolchain executable. If your compiler does not have a GCC, setup the G++ here, too.
--- End quote ---
Can you tell me, what is wrong, exact?
Configuring CodeSourcery toolchain in the same manner works fine, and it's executables also named as "arm-none-linux-gnueabi-*.exe".
Also, under Eclipse these executables working fine.
Next, I find another executables in NDK under the deeper path D:\android-ndk-r8b\toolchains\arm-linux-androideabi-4.4.3\prebuilt\windows\arm-linux-androideabi\bin - they have short "standard" names - gcc.exe, g++.exe and so on, but configuring C::B with that path also reports error.
--- Quote from: MortenMacFly on November 15, 2012, 09:47:02 pm ---I just successfully configured NDK on my PC - so it definitely works with the right setup.
--- End quote ---
Hmm, I can't undestand, why I can't start it work.
My configuration is Win7 x64; C::B 8.05 with MinGW, 32 bit; 32bit NDK.
Can you export your C::B settings for NDK and attach it?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version