![]() |
|
This thread is locked; no one can reply to it.
![]() ![]() |
1
2
|
mingw32-make replacement? |
Neil Roy
Member #2,229
April 2002
![]() |
Thomas Fjellstrom said: No reason to stop posting or anything. You'll want to note that Allegro 5 doesn't work very well with Mingw GCC 3.x. It really prefers the latest 4.x compilers due to not having broken Thread Local Storage. I have MSVC10 + Allegro 5 installed. I needed an excuse to play around with VC10 anyhow I guess. The idea behind sticking with MinGW was that I knew it, there wasn't anything new I needed to learn. MSVC10 is now free, there's no reason to stick with MinGW anymore, so I may as well learn MSVC if I'm going to be learning anything. I'm keeping the old stuff for use with old projects. I'm hoping to eventually port any older projects that I really want to work on over to MSVC + Allegro 5 once I am comfortable with it. --- |
North~
Member #12,192
August 2010
|
BillyBob said: Programming is like sex. It's sweaty, dirty work, and sometimes nothing comes out. ... um... okay. I couldn't stop myself from laughing onto the floor at that. But... wow |-3 -------------------------------------------------- If this is possible if you don't correctly initialize memory, it should be a priority of the highest order. |
gnolam
Member #2,030
March 2002
![]() |
[EDIT] -- |
MiquelFire
Member #3,110
January 2003
![]() |
[Freakin editting] --- |
LennyLen
Member #5,313
December 2004
![]() |
Neil Roy said: After all this, I figured I may as well go all the way and I uninstalled CodeBlocks and put Dev-C++ back on. That makes no sense at all, since C::B can use whatever compiler you tell it to, and can even import Dev-C++ projects. Neil Roy said: My code wasn't that fucking old, gawd. I had code I had worked on in 2009, less than two years ago, roughly 16 months ago that suddenly wouldn't compile at all. Then it was coded badly. I've got projects going back five years that still compile fine.
|
Neil Roy
Member #2,229
April 2002
![]() |
I forgot to mention, importing Dev-C++ projects wasn't working very well. The project settings were screwed up to the point that no matter what I did to correct them after an import, I still couldn't compile, I would get strange errors. BUT, when I created an empty project, then manually imported all my project files and manually set up all the options by hand, they compiled up fine. If I need to go through that much work, I may as well have Dev-C++ back on and load up the actual projects. It may be an old IDE but it works for me, I have never had a problem with it. I also installed the old MinGW to go with it. But keep in mind, this is ONLY so I can load in older projects (I have quite a few, my programming interest vary quite a bit! Oh, one other hassle, which probably could have been corrected somehow, though I couldn't find a way, was CodeBlocks, when ever I went to add a new library, it would take me to the last project folder I worked on instead of the MinGW/lib folder... then you spend a minute navigating around Windows to find the MinGW/lib folder, this gets very annoying. Like I said, lots of little things all add up and I got fed up. Note, most of the problems I had were dealing with compiling libraries that were used in some of those projects, not stuff I actually coded (which makes recoding them even worse, I can read my own code, but someone elses?!). And the makefiles that went with them. NOT my own code. Just the odd thing like the "const char *" issues where I needed to change that in a few places, little things. It just all adds up to a huge annoyance. When you correct your own code and it sill won't compile, and hours later you realize it was due to someone else's library/makefile which I absolutely don't feel like reprogramming their code and spending another day when I could just put on the older IDE/compiler... well... you get the picture. --- |
LennyLen
Member #5,313
December 2004
![]() |
Neil Roy said: Note, most of the problems I had were dealing with compiling libraries that were used in some of those projects, not stuff I actually coded (which makes recoding them even worse, I can read my own code, but someone elses?!). And the makefiles that went with them. NOT my own code. Yeah, I know that pain. I've often found other people's makefiles didn't work, even back in MinGW 3.x days. I usually, just created my own projects with the source and didn't bother with their makefiles.
|
|
1
2
|