Hi Adam
I don't have any issues locally, and seemingly not on ci.kicad-pcb.org
either, see the linked build when finished. That was with a make clean
first.
http://ci.kicad-pcb.org/job/kicad-full/14/console
2014-10-25 4:19 GMT+02:00 Adam Wolf adamw...@feelslikeburning.com:
I'm getting issues
Marco,
Great work on the conversion analysis. I finally go around to testing
this and I have to say that I prefer the asciidoc format better than the
markdown and rst formats for plain text readability. I also could not
convert the asciidoc format to pdf using your example. I always get an
Hi,
yes, that fixes it.
Regards,
Bernhard
On 24.10.2014, at 22:59, Wayne Stambaugh stambau...@verizon.net wrote:
Bernhard,
Can you please verify that this patch does indeed fix the issue on OSX
before I add this patch.
Thanks,
Wayne
On 10/23/2014 11:12 PM, Garth Corral wrote:
It appears that boost has not been made a dependency of the new tool
framework. If you are compiling without -DKICAD_SKIP_BOOST=ON, it
appears that the internal build of boost was not completed before common
library started to build. I thought this dependency was already defined
for this but I
Don't spend too much time on it--I did a complete clean and things are
looking fine.
Thanks Wayne!
Adam Wolf
On Sat, Oct 25, 2014, 10:03 AM Wayne Stambaugh stambau...@verizon.net
wrote:
It appears that boost has not been made a dependency of the new tool
framework. If you are compiling
I just checked and the common library depends on lib-dependencies which
depends on boost so boost should be built before the common library
build starts. Maybe it's an issue with CMake. Whenever I see some not
building correctly in an existing build, I generally do a make clean at
a minimum and
I've been working on packaging KiCad on MSYS2 with mingw64 and mingw32.
I have everything building including the full Python scripting.
Unfortunately our current install paths when building with mingw don't
match up with the msys/mingw file structure. The msys/mingw file
structure is the same as
Hi Wayne,
Are you using CPack for this at all? I don't know hardly anything about
Windows, but I'm looking at packaging up KiCad for OS X (which appears to
be the last piece--I had a week of successful builds!), and while I have a
shell script to do this, if you're using CPack we might as well
Hey Adam,
The msys2 project uses pacman which is the package management tool used
by arch linux. It has a very simple package build file format. One
thing it does do, is it creates a psuedo install after it builds the
package. The psuedo install is just a temporary install path with the
Sounds great.
Adam Wolf
On Sat, Oct 25, 2014 at 11:58 AM, Wayne Stambaugh stambau...@verizon.net
wrote:
Hey Adam,
The msys2 project uses pacman which is the package management tool used
by arch linux. It has a very simple package build file format. One
thing it does do, is it creates a
On 24 October 2014 16:31, Wayne Stambaugh stambau...@verizon.net wrote:
Brian,
I restored the custom FindPythonLibs.cmake file. I found an issue with
the stock version when configuring on MSYS2. I made some minor changes
to it which should make it more robust when looking for mingw python
On 25 October 2014 17:22, Wayne Stambaugh stambau...@verizon.net wrote:
I've been working on packaging KiCad on MSYS2 with mingw64 and mingw32.
I have everything building including the full Python scripting.
Unfortunately our current install paths when building with mingw don't
match up with
On 25 October 2014 15:52, Wayne Stambaugh stambau...@verizon.net wrote:
Marco,
Great work on the conversion analysis. I finally go around to testing
this and I have to say that I prefer the asciidoc format better than the
markdown and rst formats for plain text readability. I also could not
On 24 October 2014 21:17, Nick Østergaard oe.n...@gmail.com wrote:
Hello
Some background info:
I was allowed by Ajo to play around on the Jenkins build server [1] to
add automatic building of the doxygen documatation for the purpose of
having it online and always up to date. I have dumped
On 10/25/2014 4:59 PM, Brian Sidebotham wrote:
On 24 October 2014 16:31, Wayne Stambaugh stambau...@verizon.net wrote:
Brian,
I restored the custom FindPythonLibs.cmake file. I found an issue with
the stock version when configuring on MSYS2. I made some minor changes
to it which should
On 25 October 2014 22:29, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/25/2014 4:59 PM, Brian Sidebotham wrote:
I expect the other two PATH_SUFFIXES supplied to that find_path() are
wrong by the way, I've not removed them in case they are actually
correct, but generally the only
On 10/25/2014 5:14 PM, Brian Sidebotham wrote:
On 25 October 2014 17:22, Wayne Stambaugh stambau...@verizon.net wrote:
I've been working on packaging KiCad on MSYS2 with mingw64 and mingw32.
I have everything building including the full Python scripting.
Unfortunately our current install
On Sat, Oct 25, 2014 at 10:52:54AM -0400, Wayne Stambaugh wrote:
Marco,
Great work on the conversion analysis. I finally go around to testing
this and I have to say that I prefer the asciidoc format better than the
markdown and rst formats for plain text readability.
Almost everyone does
18 matches
Mail list logo
