User forums > Using Code::Blocks
Keep getting "It seems that this project has not been built yet."
Jenna:
Before the message, you should see: "Checking for existence: ...".
Make sure the dll exists in the place C::B looks for it.
EDIT:
And make sure you have no spaces or special characters in the path and the dll is on the same drive as MinGW.
Or better update your MinGW installation (I suggest TDM's build: http://tdm-gcc.tdragon.net/, or the one provided with C::B 10.5 [TDM MinGW gcc4.4]).
IceColdBeer:
--- Quote from: jens on July 21, 2010, 08:08:09 pm ---Before the message, you should see: "Checking for existence: ...".
Make sure the dll exists in the place C::B looks for it.
And make sure you have no spaces or special characters in the path and the dll is on the same drive as MinGW.
--- End quote ---
The DLL name contains no whitespaces or unusual characters. Putting the DLL on the same drive as MinGW isn't really going to help - but thanks anyway.
Ok, did the following:
1) Deleted the generated DLL from the previous build.
2) Build->Clean
3) Build->Build
4) ||=== Build finished: 0 errors, 13 warnings ===|
5) DLL created successfully 22/07/2010 10:43
6) Go to Build->Run and:
"It seems that this project has not been built yet. Do you want to build it now?"
--- Quote from: jens on July 21, 2010, 08:08:09 pm ---Or better update your MinGW installation (I suggest TDM's build: http://tdm-gcc.tdragon.net/, or the one provided with C::B 10.5 [TDM MinGW gcc4.4]).
--- End quote ---
We don't even know if MinGW tools are used to determine whether the rebuild needs to be done, so could be a waste of time upgrading.
* * * *
Code Blocks is using a GNU makefile to build the project and displays the following in the build log box when building:
"Using makefile: makefile"
This means I can also build the project outside of Code Blocks by just calling "mingw32-make.exe".
My question was how Code Blocks determines whether to do a rebuild? Does it use the MinGW tools to check or does it just check the date of the EXE or DLL internally without MinGW? I don't believe CB is using "mingw32-make.exe" to determine whether to do a rebuild, as it would have to wait for the string "is up to date" from mingw32-make.exe and this would mean starting the build in order to deteremine whether the build was upto date or not.
Jenna:
Sorry to say, but it seems you don't really want help.
--- Quote from: jens on July 21, 2010, 08:08:09 pm ---Before the message, you should see: "Checking for existence: ...".
Make sure the dll exists in the place C::B looks for it.
--- End quote ---
The message "Checking for existence:" is quite clear and tells you how (and where) C::B looks for the dll.
If it is not there, please fix your configuration in the projects properties for the appropriate targets ("Output filename" is where you have to look at).
You did not write that you use a custom makefile until your last post, but this is really important, a makefile does things C::B can not know about, because it bypasses C::B's own build-system.
In my previous post I told you what to do, but it seems you know it better.
--- Quote from: IceColdBeer on July 22, 2010, 10:53:59 am ---We don't even know if MinGW tools are used to determine whether the rebuild needs to be done, so could be a waste of time upgrading.
--- End quote ---
Yes, in custom makefile they are used, but theat's not the cause for your problem.
It's a waste of our time, if users who want help do not give important information as it should be done automatically if anyone asks for help (not only here, but in any help forum or any other situation).
IceColdBeer:
Yes, I should have mentioned that I was using my own makefile (sorry), but the original question was
--- Quote from: IceColdBeer on July 20, 2010, 02:37:39 pm ---How does Code Blocks determine whether the project has already been built?
--- End quote ---
I've had a list of responses asking to turn on compiler logging and upgrade the MinGW tools etc. which has side tracked this thread.
--- Quote from: jens on July 22, 2010, 12:20:12 pm ---Sorry to say, but it seems you don't really want help.
--- End quote ---
I only wanted to know how Code Blocks determines whether the project has already been built? Once I know that, I can look into the problem. I thought I'd be taking to a developer on CB on this thread who could give me a quick answer.
I don't think it something anyone would know unless they'd written that part of the software in CB.
It looks like I'm going to have to live with the message ("It seems that this project has not been built yet. Do you want to build it now?"), but it's no big deal and can just say no.
I think Code Blocks is a great piece of Software Engineering :)
Jenna:
--- Quote from: IceColdBeer on July 22, 2010, 12:47:12 pm ---I thought I'd be taking to a developer on CB on this thread who could give me a quick answer.
--- End quote ---
I am a developer of C::B and you still did not do what I told you (and I gave you the answers you asked for):
--- Quote from: jens on July 22, 2010, 12:20:12 pm ---[...]
--- Quote from: jens on July 21, 2010, 08:08:09 pm ---Before the message, you should see: "Checking for existence: ...".
Make sure the dll exists in the place C::B looks for it.
--- End quote ---
The message "Checking for existence:" is quite clear and tells you how (and where) C::B looks for the dll.
If it is not there, please fix your configuration in the projects properties for the appropriate targets ("Output filename" is where you have to look at).
[...]
--- Quote from: IceColdBeer on July 22, 2010, 10:53:59 am ---We don't even know if MinGW tools are used to determine whether the rebuild needs to be done, so could be a waste of time upgrading.
--- End quote ---
Yes, in custom makefile they are used, but theat's not the cause for your problem.
[...]
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version