Community
Participate
Working Groups
Build Identifier: 20110916-0149 I'm attaching a screenshot showing my configuration. Essentially, I have a project that doesn't use Make. I've unchecked the "Use default command", blanked out the "Build command" text box, and provided commands for the Build & Clean "targets" under the behavior tab. In Windows, when I do a build or a clean, these commands are executed. In Linux, they are just echoed out to the build console, but they aren't actually executed. Here is an example: **** Build of configuration linux64-bindings for project SimExternalInterfaces **** python setup.py bdist_egg --plat-name=linux64 build_ext build --build-platlib=build/linux64 **** Build Finished **** Nothing has happened. Reproducible: Always Steps to Reproduce: 1. Uncheck use default build command and blank out the build command 2. In the behavior tab, add something like touch blah.txt for the Build behavior 3. Do a build, note that touch blah.txt was echoed to the console, discover that blah.txt wasn't created
Created attachment 208708 [details] Screenshot of how things are setup. This is from Windows, but setup is basically identical in Linux
(In reply to comment #0) I think you misinterpreted the setup. In "Build command" you should insert your actual build command. On the behavior tab you insert the "make targets" that are used for incremental build/clean etc. Eclipse will then call "BUILD_COMMAND MAKE_TARGET" So MAKE_TARGET is a kind of argument (the syntax is borrowed from original make). In your case where you defined no build command you will get the following command line: python setup.py bdist_egg --plat-name=linux64 build_ext build --build-platlib=build/linux64 Notice the space at the beginning which prevents the execution of this command. I don't know why this works under Windows but the principal behavior of Eclipse is identical. see Help page http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.cdt.doc.user%2Freference%2Fcdt_u_prop_build.htm Your setup is a little tricky as you have different commands for build and clean. You could try to create a small Makefile has two possible make targets for build and clean.
