User forums > Using Code::Blocks

Using Code::Blocks with HeeksCAD

<< < (2/3) > >>

jonas thomas:
I found the source of my confusion :lol:
[/quote]
If you use custom makefiles, you have to name your targets as the appropriate makefile rules,
[/quote]
I went to project>properties (tab build targets)
It had these settings:
Output filename: HeeksCad
Execution working directory:/usr/local/bin

That was the source of my confusion.  After thinking about what you said it did the following:
Was:
Output filename: HeeksCad
change to read:
Output filename: /usr/local/bin/HeeksCad
When I did that I got a permission denied message which is the point where the light clicked on.

(I suppose I need a sudo somewhere to gain access to /usr/local/bin....)
To get around the sudo issue I changed to the following settings
Output filename: ../HeeksCAD_Executable_NotTheBestSolution/bin/HeeksCAD
Execution working directory:/usr/local/bin
(and copied the graphics over to:
/home/jonas/HeeksCAD_Executable_NotTheBestSolution/share/heekscad/bitmaps
/home/jonas/HeeksCAD_Executable_NotTheBestSolution/share/heekscad/icons

So... what is the function of the "Execution working directory:/usr/local/bin" ?

This is a real ugly solution but it works for me, so I can study the code to gain some more understanding on how this works.

Thanks....



deadneurons:
OK, I continued the compilation, but got an error during linking,
this is the last part of the error:


--- Code: ---g++: obj/Release/src/HeeksCAD.res: No such file or directory
Process terminated with status 1 (7 minutes, 42 seconds)
0 errors, 28 warnings

--- End code ---


EDIT: I believe it's related to resource file, unfortunately it's out of my league.

jonas thomas:

--- Quote from: deadneurons on June 06, 2009, 07:53:07 pm ---I'm also watching the progress of HeeksCAD, I'm a hobbycnc'ist.
Can you try this cbp, place it inside the HeeksCAD dir where src, interface, tinyxml are,
You must change the path for stdafx.h, on some headers,  changed the path of some includes in HeeksCADInterface.cpp.
you also have to specify the casroot in global variables.
I didn't finish the compilation but it's halfway through when I canceled it since I already have it built via makefile.
Hopefully this works.

--- End quote ---

This is starting to digress into a discussion about Heekscad.   Mr. Code Blocks man has a tendency to lock down threads when that happens ;) ...
I tried your project file and was getting all kinds of nasty stuff about that casroot.
I think your using the Opencascade linux download instead of Adam Powell .deb file (That library is set up to debian standards which will make your life much easier if you use the .deb file.)  Anyway... My suggestion is you might want to take this discussion http://groups.google.com/group/heekscad-devel?hl=en

deadneurons:
you're right, pardon me, just trying to help.
this should be my last post.

jonas thomas:

--- Quote from: deadneurons on June 06, 2009, 08:25:46 pm ---you're right, pardon me, just trying to help.
this should be my last post.

--- End quote ---
Thanks (Your making feel bad now), besides.... I finally reached my initial objective has been reached... ie...
Keeping HeeksCAD to run via Code::Blocks It might be ugly, but it's enough for me to dissect.
This is so cool:
Code:Blocks, wxwidgets, C++, OpenCascade via HeeksCAD..  I need to spend a month snooping under the hood to see how this all works...
Anyway... I would like to eventually figure to setup up Code:Blocks this up properly to say in sync with the heeksCAD in the google code repository. (My clever attempt to bring the  back on C::B topic)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version