i dunno where this problem came from it was working fine before (as previously post) and as why i was so frustrated you need to stop worrying about typing out a long conversation when dealing with someone oviously less experienced in C++ and coding in gernal
TY FOR THE HELP TED
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You have set, either deliberately or accidentally, the option -lobjc, which is an option to link an Objective C program, which for 99.999% of the people makes no sense. You need to find where, in either your project or compiler options, that has been set and turn it off. You have set a number of other options as well, like one that turns off linking the standard library, which seem strange as well.
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the first instance you put your project in "c:\dev-cpp\", apart from not being a good idea generally to pollute the installation folder, there is a bug in Dev-C++ that causes projects in that folder or sub-folders of that to sometimes fail .
In the second you placed your project on the Desktop. The path to that folder "C:\Documents and Settings\<username>\Desktop\" contains spaces, and these also sometimes cause build failure. Use a different folder.
> all it does is compile shit like Makefile.win
Are you as clueless as you sound? makefile.win is not compiled. It is generated by Dev-C++ as input to the make utility, which is a build management tool. It determines what needs to be compiled and linked to generate your executable. It is essential to your build and is in not 'sh*t' of any kind. You can rant and scream if you like, but it just makes you sound unpleasant, and more than a little stupid.
Your log only shows the linker stage, so compilation must have been successful, you must have at least main.o in your project file. Do a Execute->Rebuild All and post that log so that we can see how you set up the whole project. You may find in fact that that (and the space-free path) solves your problem.
Don't bother posting your log if you are going to insert unnecessary obscenities into the path names. To have given yourself that user name suggests that you might be a particularly unpleasant individual. You certainly exhibit a lack of patience and thought clarity needed to successfully program. You need to calm down, and slow down, and possibly wait for responses here before floundering around with unnecessary re-installations.
What code are you compiling? Your log suggests that it is a Windows GUI app, and that it requires wininet to be linked. Are you perhaps trying to run before you can walk? I suggest that you get a plain vanilla console app to build before you start pulling in additional libraries or GUI development. Besides Dev-C++ is not a great tool for GUI development.
Clifford
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Compiler: Default compiler
Building Makefile: "C:\Dev-Cpp\Makefile.win"
Executing make...
make.exe -f "C:\Dev-Cpp\Makefile.win" all
g++.exe -DDEBUG lib/ccpexe.o -o "Cppexe.exe" -L"C:/Dev-Cpp/lib" -mwindows -lobjc -g3 -nostdlib -s
C:\Dev-Cpp\Bin..\lib\gcc\mingw32\3.4.2........\mingw32\bin\ld.exe: cannot find -lobjc
collect2: ld returned 1 exit status
make.exe: *** [Cppexe.exe] Error 1
Execution terminated
WTF IS GOING ON???
cannot find -lobjc
ld returned 1 exit status
C:\Dev-Cpp\Makefile.win [Build Error] [Cppexe.exe] Error 1
REBUILD ALL LOG:
> Compiler: Default compiler
Building Makefile: "C:\Dev-Cpp\Makefile.win"
Executing make clean
rm -f ../dev/main.o Project1.exe
g++.exe -DDEBUG -c ../dev/main.cpp -o ../dev/main.o -I"C:/Dev-Cpp/lib/gcc/mingw32/3.4.2/include" -I"C:/Dev-Cpp/include/c++/3.4.2/backward" -I"C:/Dev-Cpp/include/c++/3.4.2/mingw32" -I"C:/Dev-Cpp/include/c++/3.4.2" -I"C:/Dev-Cpp/include" -g3
../dev/main.cpp: In function
BOOL FTP_UploadToServer()': ../dev/main.cpp:101: warning: passing NULL used for non-pointer converting 7 ofBOOL FtpGetFileA(void, const CHAR, const CHAR*, BOOL, DWORD, DWORD, DWORD)'../dev/main.cpp:149: warning: passing NULL used for non-pointer converting 5 of `BOOL FtpPutFileA(void, const CHAR, const CHAR*, DWORD, DWORD)'
g++.exe -DDEBUG ../dev/main.o -o "Project1.exe" -L"C:/Dev-Cpp/lib" -mwindows lib/libwininet.a -g3
Execution terminated
Compilation successful
i dunno where this problem came from it was working fine before (as previously post) and as why i was so frustrated you need to stop worrying about typing out a long conversation when dealing with someone oviously less experienced in C++ and coding in gernal
TY FOR THE HELP TED
We are going around in circles. You have now put your source in c:\dev\ but left your project file in c:\dev-cpp\ contarary to previous advice!
ive also tryed using CODEBLOCKS but it doesnt work etheir
You have set, either deliberately or accidentally, the option -lobjc, which is an option to link an Objective C program, which for 99.999% of the people makes no sense. You need to find where, in either your project or compiler options, that has been set and turn it off. You have set a number of other options as well, like one that turns off linking the standard library, which seem strange as well.
Wayne
thanks... that helped sorta wayne, but now my problem still consists it will not compile into an .exe
heres my compile log
Compiler: Default compiler
Building Makefile: "C:\Dev-Cpp\Makefile.win"
Executing make...
make.exe -f "C:\Dev-Cpp\Makefile.win" all
g++.exe lib/ccpexe.o -o "Cppexe.exe" -L"C:/Dev-Cpp/lib" -mwindows lib/libwininet.a
Execution terminated
Compilation successful
thanks again any help is appreciated
all i get is a Makefile.win
REINSTALLING>...
why can i not compile an .exe it was working perfectly before?
all it does is compile shit like Makefile.win
Compiler: Default compiler
Building Makefile: "C:\Documents and Settings\FUCK You\Desktop\COMPILE\Makefile.win"
Executing make...
make.exe -f "C:\Documents and Settings\FUCK You\Desktop\COMPILE\Makefile.win" all
g++.exe main.o Project1_private.res -o "Project1.exe" -L"C:/Dev-Cpp/lib" -mwindows ../../../../Dev-Cpp/lib/libwininet.a
Execution terminated
Compilation successful
In the first instance you put your project in "c:\dev-cpp\", apart from not being a good idea generally to pollute the installation folder, there is a bug in Dev-C++ that causes projects in that folder or sub-folders of that to sometimes fail .
In the second you placed your project on the Desktop. The path to that folder "C:\Documents and Settings\<username>\Desktop\" contains spaces, and these also sometimes cause build failure. Use a different folder.
> all it does is compile shit like Makefile.win
Are you as clueless as you sound? makefile.win is not compiled. It is generated by Dev-C++ as input to the make utility, which is a build management tool. It determines what needs to be compiled and linked to generate your executable. It is essential to your build and is in not 'sh*t' of any kind. You can rant and scream if you like, but it just makes you sound unpleasant, and more than a little stupid.
Your log only shows the linker stage, so compilation must have been successful, you must have at least main.o in your project file. Do a Execute->Rebuild All and post that log so that we can see how you set up the whole project. You may find in fact that that (and the space-free path) solves your problem.
Don't bother posting your log if you are going to insert unnecessary obscenities into the path names. To have given yourself that user name suggests that you might be a particularly unpleasant individual. You certainly exhibit a lack of patience and thought clarity needed to successfully program. You need to calm down, and slow down, and possibly wait for responses here before floundering around with unnecessary re-installations.
What code are you compiling? Your log suggests that it is a Windows GUI app, and that it requires wininet to be linked. Are you perhaps trying to run before you can walk? I suggest that you get a plain vanilla console app to build before you start pulling in additional libraries or GUI development. Besides Dev-C++ is not a great tool for GUI development.
Clifford