|
|
|
| setting up |
|
William Labbett
Member #4,486
March 2004
 |
Hi, I'm trying to get allegro working with codeblocks. I've installed CodeBlocks. Do I need to set up the paths next ?
|
|
LennyLen
Member #5,313
December 2004
 |
Go to Settings->Compiler and Debugger->Toolchain Executable. You'll want it looking like this (though you may have to change the installation directory): http://www.allegro.cc/files/attachment/594188 Then when you want to compile, go to Project->Build Options->Linker settings, then add the allegro library. edit: If you're running under Vista, you need to do a few more things. See here.
|
|
William Labbett
Member #4,486
March 2004
|
Here's what it looks like atm http://www.allegro.cc/files/attachment/594189 edit : which directory should unzip allegro to ? My codeblocks directory is C:/CodeBlocks
|
|
LennyLen
Member #5,313
December 2004
|
Where do you have gcc installed? This is where the Compiler Installation Directory should be set to. At the moment, yours is pointing to your Code::Blocks directory. If this is where you've installed gcc, it's better to keep them seperate. edit: Quote: which directory should unzip allegro to It really doesn't matter, when you compile Allegro, it will put the .h and .a files in the right place. You can make things even easier for yourself once Code::Blocks is up and running by installing the Allegro DevPak, which will do everything for you.
|
|
William Labbett
Member #4,486
March 2004
|
thanks, I installed a version of CodeBlocks which comes with mingw32. I used the command ggc -v from C:\CodeBlocks\bin and I got the version Sounds like you think it's better to keep them seperate.
|
|
LennyLen
Member #5,313
December 2004
|
Quote: Sounds like you think it's better to keep them seperate. Mostly because I use the nightly builds, so when I install a new one, I just delete the entire Code::Blocks directory and unzip the new files. By the way, the version that comes with gcc is an older version (it's almost two years old now). The latest nightly build is stable and has a lot more features than the 1.0RC2 version (and despite the fact that they call the RC2 release the stable release, the nightly builds are usually actually more stable). edit: the nightly builds are here.
|
|
William Labbett
Member #4,486
March 2004
|
thanks, I followed the instructions. http://www.allegro.cc/files/attachment/594190 Now I'm wondering if I have to change my PATH.
|
|
LennyLen
Member #5,313
December 2004
|
Quote: Now I'm wondering if I have to change my PATH. You don't need any entries in the path to run Code::Blocks, or even for MinGW if you are using Code::Blocks. It's still a good idea to set the MINGDIR environment variable and add your MinGW\bin directory to the path though should you ever wish to compile from the command line. Quote: Also if I have to complile allegro. You can manually compile it if you want to. Otherwise, you can get the precomiled binaries and just copy the files to the correct places, or even easier, just use the DevPak (the latest version is only 4.2.1 however).
|
|
William Labbett
Member #4,486
March 2004
|
thanks Lenny, not sure what to do to install the devpak though
|
|
LennyLen
Member #5,313
December 2004
|
Got to Plugins->Dev-C++ DevPak updater/installer. Change the update server to devpaks.org and look in the Allegro category.
|
|
William Labbett
Member #4,486
March 2004
|
Thanks very much for all the help. edit : sussed it out myself but I get this as the build output :- "colour_converter - Release" uses an invalid compiler. Skipping...
Nothing to be done.
Anyone know what's wrong ?
|
|
LennyLen
Member #5,313
December 2004
|
I've only ever got that error when the Compiler Installation Directory is set incorrectly.
|
|
William Labbett
Member #4,486
March 2004
|
I don't recall installing mingw32. I downloaded a zip file mingwm10_441.zip
|
|
LennyLen
Member #5,313
December 2004
|
That dll is needed for the Code::Blocks IDE to run. If you want Code::Blocks to use MinGW as the compiler (Code::Blocks can be used with many compilers), then yes, you do have to have MinGW installed on your system.
|
|
William Labbett
Member #4,486
March 2004
|
Hi, Don't know if there's a simple answer to this. Here's the compiler output - Compiling: main.c Linking console executable: bin\Release\colour_converter.exe Execution of 'mingw32-g++.exe -o bin\Release\colour_converter.exe obj\Release\main.o -s' in 'C:\codeblocks\1stproject\colour_converter' failed. Nothing to be done.
|
|
GullRaDriel
Member #3,861
September 2003
 |
Yeah. It's because the exe is already created and that.... there is nothing more to do ! Check that /bin/release directory, your exe should be there ! "Code is like shit - it only smells if it is not yours" |
|
William Labbett
Member #4,486
March 2004
|
It doesn't seem to be.
|
|
GullRaDriel
Member #3,861
September 2003
|
Yeah, my bad. I missed the end of the line. BTW, what is that '-s' you seem to have when linking ? "Code is like shit - it only smells if it is not yours" |
|
William Labbett
Member #4,486
March 2004
|
I don't know. The makefile's made automatically i think.
|
|
Arthur Kalliokoski
Second in Command
February 2005
 |
The '-s' means strip out debugging info from the output. To the OP: Get a command prompt and type "set > env.txt" and post env.txt here. They all watch too much MSNBC... they get ideas. |
|
William Labbett
Member #4,486
March 2004
|
Sorry but in which directory ?
|
|
Arthur Kalliokoski
Second in Command
February 2005
|
It doesn't matter which directory you type SET in. It's a cmd.exe builtin. They all watch too much MSNBC... they get ideas. |
|
William Labbett
Member #4,486
March 2004
|
http://www.allegro.cc/files/attachment/594197 I typed it but I think nothing happened or if it did I can't find env.txt .
|
|
Arthur Kalliokoski
Second in Command
February 2005
|
"dir env.txt"? They all watch too much MSNBC... they get ideas. |
|
Mark Oates
Member #1,146
March 2001
 |
Oh hey, you know what I did? Uninstall everything, install Dev-Cpp (with MinGW), then install the latest version of Code::Blocks from the nightly build dealie, and it automatically found the MinGW installed from Dev-Cpp. Downloaded OpenLayer, following the easy procedure in my Installing OpenLayer video. Lickity smack bam! everything was ready to go. -- |
|
|
|
