Re: Debugger initialization commands to debug in wxWidgets. « Reply #2 on: June 02, 2011, 08:22:48 am ». Of course I link with debug dynamic library. I think it is a path problem, gdb doesn't found where src are loated. I'm trying to add: Code: [Select].

Usually 'a cross-compiler from X to Y' would mean, 'a compiler that itself runs on X, but produces binaries that run on Y'. So you're asking for a compiler that runs on Windows and produces Linux binaries. Is that what you want? The usual way to do it is to compile for linux on linux. The usual reason for cross-compiling is that Y is not a viable development environment (e.g. Because it's a mobile phone, set-top box, Roomba, etc), maybe you'd be better off finding a Linux IDE you can live with?

– Jan 22 '11 at 19:31. Overview: • Install cygwin, with development packages • • Extract the tarball ( tar xvjf crosstool-ng*) • Run./configure • When configure complains about a missing tool, go back to cygwin setup and install the corresponding package (e.g. Flex, libtool, ncurses-devel) You'll need at least the following: • Devel/gperf • Devel/bison • Devel/byacc • Devel/wget • Devel/patch • Devel/make (GNU version) • Devel/automake 1.10+ • Libs/libncursesw10 • Libs/libncursesw10-devel • make • make install • Create a new directory for building the cross-compiler, e.g. /usr/src/cross-linux-gnu-root • Enable system-wide case sensitivity support in the registry (see ) • Mount the directory case-sensitive (e.g. Mount c:/cygwin/usr/src/cross-linux-gnu-root /usr/src/cross-linux-gnu -o binary,posix=1) • From inside the cross-compiler build directory, ct-ng menuconfig • In the menus, set target architecture to x86 (probably) and subarchitecture to i686 (avoids, thanks osm0sis), target kernel to linux, and target C library to glibc, and enable the C++ compiler.

• To work around, also enable EXPERIMENTAL in Paths and misc options then, go in Companion tools (at top-level) and enable Build some companion tools and then make 3.81 (Thanks osm0sis) • wget has issues with the latest kernel.org certificates so use the.wgetrc method in this accepted answer: (Thanks osm0sis) • Currently 3 file patches are required to avoid further errors: • as mentioned in the comments •, and • (Thanks Duncan Calvert & osm0sis) • ct-ng build Of course, this is NOT going to enable you to build linux applications from inside Visual Studio. (VS2010 and later let you build with other toolchains such as gcc, but you'd need an appropriate toolchain description in addition to the cross-compiler built by crosstool-ng). But you'll have a working g++-linux-gnu, which you can either run directly or using a Makefile. NOTE: Building the cross-compiler takes a LONG time. Osm0sis has provided, along with his notes on building the cross-compiler (used to update this answer). What's a 'Windows/Linux' binary?

AFAIK, mingw is just gcc-for-windows, and makes PE executables. Frontech Tv Tuner Jil 0606 Driver Windows 7 here. Linux binaries must be in linux-compatible formats, of which ELF is the most popular. I'm in the middle of the ct-ng build step now, trying to make sure my answer is as complete as possible and includes solutions to any gotchas along the way. And yes, the compiler I'm building will generate ELF executables which are dynamically linked against glibc (and other libraries as appropriate). – Jan 22 '11 at 21:30. Your best bet is to use a cross platform IDE like that can import MSVC projects, and generate a Makefile for Linux, which you can then run on a Linux (with even the same program if you so wish). So your work flow would then look something like the following: Code, Compile, and debug on MSVC ->import into Code::Blocks & generate Makefile ->test compile and debug with GCC ->copy to Linux with Code::Blocks ->test compile & debug on Linux It's a little obtuse, probably, but at least Code::Blocks takes care of a lot of those small details with things like Makefiles, and what not.

I don't believe there are any compilers that allow you to compile on Windows and then take the resulting binary and run it on a Linux machine. Your best bet is to set up two development environments, one on Windows and one on Linux. Do most of your development and debugging in the Windows environment if that's what suits you, then frequently compile and test under Linux to be sure your code is truly cross-platform. You'll also want to use a cross-platform build system and testing framework. I recommend using and, respectively. Compile to Linux from Windows without to use virtualization or cross compiler but only natively via coLinux Create native Linux executable files without leave (reboot) windows. C/C++ Compiling for Linux under Windows through Cooperative Linux The fastest switching between Windows and Linux through ALT-TAB (no restarting or rebooting needed).