Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What is the last letter in the word "SlickEdit":
How many LETTERS are in the following? "a1b2c3":
Which number is missing?  "12345689":

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: avnerm
« on: May 06, 2008, 12:11:11 AM »

I'm trying to compile a cpp file using SlickEdit.
When I run "make bgmBgModeller.o" from the command line (outside SE) the following command line is dispatched:

/usr/bin/gcc bgmBgModeller.cpp -fPIC -DEXP_PRODUCT_STAMP="Product_00999" -DEXP_PRODUCT="Equinox" -DEXP_VERSION="2.09.01" -DEXP_FC_RELEASE="8" -D_GNU_SOURCE -DEXP_KERNEL_MAJOR=2 -DEXP_KERNEL_MINOR=6 -DEXP_KERNEL_RELEASE=24 -Wall -fsigned-char -fmessage-length=90 -Woverloaded-virtual  -DEXP_GCC_MAJOR=4 -DEXP_GCC_MINOR=1 -march=core2 -DEXP_ARCH=core2 -DEXP_CPU_FAMILY_INTEL -DEXP_MMX -DEXP_SSE  -Wno-long-long -Wno-attributes -pedantic -DEXP_DEBUG -ggdb    -DEXP_DEVEL -DEXP_PROFILING    -I/home/amoshkovitz/views/equinox-v2.09.01/tree -I/home/amoshkovitz/views/equinox-v2.09.01/exportedObjects/dbg-gcc4-core2/tree -I/home/amoshkovitz/views/equinox-v2.09.01/derivedObjects/dbg-gcc4-core2/dynamic/objects/tree/algorithms/bgModelling/src    -c -o /home/amoshkovitz/views/equinox-v2.09.01/derivedObjects/dbg-gcc4-core2/dynamic/objects/tree/algorithms/bgModelling/src/bgmBgModeller.o

but when I run it with SE I get:
cc -c -g   -o "Debug/bgmBgModeller.o" "/home/amoshkovitz/views/equinox-v2.09.01/tree/algorithms/bgModelling/src/bgmBgModeller.cpp"

I adjusted the following settings in Project / Project Properties
In the "Build" tab I selected "Build with a user-maintained makefile ..."
In the "Build" tab I filled in "make" in the "run from dir:" field.
I started SE from the terminal that launches the correct make flags, so I'm expecting SE to have the same environment settings (e.g. PATH)

Why doesn't SE produce the same make flags?

Thanks,
Avner
Posted by: hs2
« on: November 26, 2007, 04:27:27 PM »

Seems that msys is quite similar to a cygwin shell (I think).
Try the 'mount'/'pwd' commands to check your location and the mapping of the Windows paths (maybe adjust '/etc/fstab') to retrieve and 'cd' to the right (bash) path to your project directory. After that you should be able to run './configure' etc.
Good luck,
HS2
Posted by: spowers
« on: November 26, 2007, 03:58:33 PM »

I got this to the point where it will run a bash command from SE.

The problem I'm having now is directing it towards the ./configure command.

the configure file is not located under the msys directory so I'm not sure how to navigate to it through the bash shell


Any ideas?
Posted by: dunkers
« on: November 14, 2007, 02:05:19 PM »

Ah, OK.
Posted by: hs2
« on: November 14, 2007, 12:07:25 PM »

In fact im using a 'bashcmd.cmd' batch script containing this single line e.g. as build tool command in SE.
In the example 'A && B' the '&&' operator means 'do B if A didn't set ERRORLEVEL to != 0'.
In this case it's just a method to do mult. things in one script line b/c SET doesn't set ERRORLEVEL.
HS2
Posted by: dunkers
« on: November 14, 2007, 11:50:04 AM »

That's interesting, hs2. What does the && do? I can feel a useful learning experience coming on :)

Posted by: hs2
« on: November 14, 2007, 10:55:35 AM »

Right. This is what I'm simply using:
Quote
@set PATH=<percent>windir<percent>\system32;<percent>windir<percent>&&<cygwin prefix>\bin\bash.exe -i -c <percent>*
to launch cygwin commands.
(There was a requirement to be able to start other (win) tools as well. Hence the cygwin paths are appended to the PATH given.)
HS2
Posted by: dunkers
« on: November 14, 2007, 10:37:59 AM »

The path Cygwin needs to run itself is different, and separate, to the path a Cygwin app needs for Cygwin to run it.
Posted by: hs2
« on: November 14, 2007, 01:18:47 AM »

cygwin itself needs a few system DLLs in system32 to run. Hence I (re-)set the win path to 'windir;windir/system32' and let bash do the rest using .bashrc/.bash_profile incl. setting up the cross toolchain env. HS2
Posted by: dunkers
« on: November 14, 2007, 12:17:25 AM »

Hard to tell. Any that GUI app that load up DLLs or similar probably do, but since we're talking the application director or /windows and /windows/system32 a very short path normally covers an awful lot. Periodically I prune the path to something decent and next time I look there's a new lot rubbish. I think it breeds! Either way, there's not much of a need for having a Windows path in Cygwin at all for compiling.

I also set the .bash_profile but there's an added complication in that I use a cross compiler for this project. Technically I could leave that on the bash path but if I've gone to the hassle of trimming all the Windows stuff out I don't see the point of not doing the same for Cygwin :)
Posted by: jbhurst
« on: November 13, 2007, 09:57:20 PM »

@Dunkers:

Do any "Windows" (i.e. Windows GUI) programs actually use the PATH variable?

I tend to delete most of the entries in PATH on Windows, and leave it set up just for command-line stuff. The GUI programs seem to work, I guess by virtue of their shortcuts starting them in their own directories.

Then in my Cygwin .bash_profile I append (or prepend) any necessary Cygwin/bash-specific stuff.

Regards

John Hurst
Wellington, New Zealand
Posted by: dunkers
« on: November 13, 2007, 09:48:41 PM »

For your reference, the way I do this is to click the Advanced button (on the build/rebuild setup dialog) and enter a new environment variable along these lines:

Code: [Select]
Set PATH=/opt/ppctools/tools/bin:/usr/local/bin:/usr/bin:/usr/sbin:/bin:/sbin
SE sets that when it starts up the shell, so make can be found. The reason I do this instead of using the Windows path is because... well, have you seen the Windows path? About 6 trillion lines long and full of dupes and pointing to tons of stuff that isn't relevant to Cygwin. Compiling something like a kernel would just fail because there was no environment space left.

Posted by: spowers
« on: November 13, 2007, 04:47:28 PM »

I think I fixed it... I had to set the windows path variable to my minGW installation directory.
Posted by: MartyL
« on: November 13, 2007, 04:24:22 PM »

If you have your own makefile, the easiest thing to do would be to change your build command to use it.

Make sure you change the "Run from dir" in Project Properties > Tools to point to the directory with your makefile. Change the "Command line" to be "make" (add parameters as needed) and make sure to uncheck "Command is Slick-C macro".

Hope this helps!
Posted by: spowers
« on: November 13, 2007, 03:55:28 PM »

I've tried using "make makefile" in the command line of the Build command but it responds with:


'make' is not recognized as an internal or external command,
operable program or batch file.

I have both MinGW and Cygwin installed but I am directing to the MinGW GCC compiler