Comments on: haXe & Eclipse build settings http://www.martijndevisser.com/blog/2006/haxe-eclipse-build-settings/ Martijn de Visser on User Experience, Front End technology (and whatnot). Tue, 16 Feb 2010 13:58:41 +0100 http://wordpress.org/?v=2.9.2 hourly 1 By: obiwan http://www.martijndevisser.com/blog/2006/haxe-eclipse-build-settings/comment-page-1/#comment-23 obiwan Thu, 19 Jul 2007 08:00:50 +0000 http://www.martijndevisser.com/blog/2006/haxe-eclipse-build-settings/#comment-23 to be more precise : create an external with /bin/sh as location, ${project_loc} as a working directory, and use the -c option of sh, so in the arguments you can ut something like : -c "/Users/me/Sites/Eclipse/.compilation-bash-scripts/buildAndRun.sh ${project_loc} ${project_name}" When doing something like this, the buildAndRun.sh file you created will receive ${project_loc} and ${project_name} as two variables that will be accessible as $1 and $2 in the .sh script... Dunno if i'm really clear, sorry for my english i'm french :p... but it's actually a really good way to avoid creating one external tool per project. to be more precise : create an external with /bin/sh as location, ${project_loc} as a working directory, and use the -c option of sh, so in the arguments you can ut something like : -c “/Users/me/Sites/Eclipse/.compilation-bash-scripts/buildAndRun.sh ${project_loc} ${project_name}”

When doing something like this, the buildAndRun.sh file you created will receive ${project_loc} and ${project_name} as two variables that will be accessible as $1 and $2 in the .sh script…

Dunno if i’m really clear, sorry for my english i’m french :p… but it’s actually a really good way to avoid creating one external tool per project.

]]> By: obiwan http://www.martijndevisser.com/blog/2006/haxe-eclipse-build-settings/comment-page-1/#comment-22 obiwan Thu, 19 Jul 2007 07:47:07 +0000 http://www.martijndevisser.com/blog/2006/haxe-eclipse-build-settings/#comment-22 Actually you really don't need to crete one external tool per project. You can pass variables to a .sh script like ${project-name} when executing it from the eclipse external tools menu. So you just need one script which takes project name and path as paramaters, what eclipse can do. Actually you really don’t need to crete one external tool per project.
You can pass variables to a .sh script like ${project-name} when executing it from the eclipse external tools menu.

So you just need one script which takes project name and path as paramaters, what eclipse can do.

]]>