Search found 372 matches
- Sun Jul 19, 2015 1:44 am
- Forum: Path/CAM
- Topic: libarea, used in Path Workbench
- Replies: 21
- Views: 7240
Re: libarea, used in Path Workbench
IMO the CMakeLists.txt file could be simplified a lot: remove project(area) remove cmake_minimum_required(VERSION 2.4) add_definitions(-fPIC) is wrong. This should be set as set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC") because add_definitions should only be used for -D Define the optio...
- Sun Jul 19, 2015 1:13 am
- Forum: Developers corner
- Topic: git access
- Replies: 42
- Views: 8870
Re: git access
Ok, I completely shut off my cronjob that was pulling from Source Forge and pushing to github. I did that just in case something weird happens over at Source Forge.
Goodbye Source Forge- it was a good run for awhile...
Goodbye Source Forge- it was a good run for awhile...
- Sat Jul 18, 2015 2:35 pm
- Forum: Path/CAM
- Topic: libarea, used in Path Workbench
- Replies: 21
- Views: 7240
Re: libarea, used in Path Workbench
I just cleaned up the BSD 3-clause licensing for the files in libarea. Dan and Geoff had been a bit lax in how they applied them earlier. See my copy of correspondence between the three of us as backing up the license. https://github.com/danielfalck/FreeCAD/blob/path_area/src/Mod/Path/libarea/kurve/...
- Sat Jul 18, 2015 12:26 am
- Forum: Developers corner
- Topic: git access
- Replies: 42
- Views: 8870
Re: git access
Would this be the final incident to cause us to abandon SF?
- Fri Jul 17, 2015 10:11 pm
- Forum: Path/CAM
- Topic: libarea, used in Path Workbench
- Replies: 21
- Views: 7240
Re: libarea, used in Path Workbench
If the area lib is together with the other freecad libs, then freecad will pick it up automatically. I think this is the correct way to do it, all libraries compiled together with freecad should stay together and not go to system folders... Thanks for commenting Yorik. area.pyd (area.so on Linux) i...
- Thu Jul 16, 2015 10:43 pm
- Forum: Path/CAM
- Topic: libarea, used in Path Workbench
- Replies: 21
- Views: 7240
Re: libarea, used in Path Workbench
As for the compiling (and PPA) documentation needs to be updated for new dependency. For Ubuntu: libboost-python-dev Beyond that it compiles fine on Ubuntu. There is something i would like to see changed if possible. Running cmake infroms the user libarea will be installed in /usr/local/lib folder ...
- Thu Jul 16, 2015 2:59 am
- Forum: Path/CAM
- Topic: libarea, used in Path Workbench
- Replies: 21
- Views: 7240
libarea, used in Path Workbench
This might be a good place to discuss 'libarea' the pocketing/profile generating library that we have adapted from HeeksCNC to use with the Path workbench. So far it is only used for one version of Profiling in Path but I intend on using it with pocketing too. In my experience with HeeksCNC, it does...
- Thu Jul 16, 2015 2:55 am
- Forum: Path/CAM
- Topic: area.pyd VC9 32 bit
- Replies: 4
- Views: 1508
Re: area.pyd VC9 32 bit
Please test this, when you can:
https://github.com/danielfalck/FreeCAD/tree/path_area
I removed a lot of files that aren't applicable to our workbench and adapted the CMakeLists.txt file to FreeCAD.
https://github.com/danielfalck/FreeCAD/tree/path_area
I removed a lot of files that aren't applicable to our workbench and adapted the CMakeLists.txt file to FreeCAD.
- Wed Jul 15, 2015 12:01 pm
- Forum: Path/CAM
- Topic: Path module merged in master!
- Replies: 79
- Views: 22912
Re: Path module merged in master!
profile.png Why are there two different GUI operations for "Profile"? Would it be possible to decide which action based on actual selected item(s)? Also, are these Also, When selecting multiple faces for a profile, only the one face is processed. I expect to have all the faces processed. ...
- Wed Jul 15, 2015 1:05 am
- Forum: Path/CAM
- Topic: Path module merged in master!
- Replies: 79
- Views: 22912
Re: Path module merged in master!
Hi Mark, Sorry for the lack of a tutorial so far. I've been super busy with work and side work lately. A lot of things have been pretty experimental (to say the least) so far. Here is a little bit of info on how I have been doing things: 1. Create the project- define the file to output gcode to in t...