On Mon, Sep 29, 2014 at 09:37:38PM -0500, inkblotter wrote:
I have very recently built a new 64-bit linux system, with a new GPU.
Of course, I wanted to build kicad on this new system.
I have installed cuda and built wxWidgets 3.0.1 and I really look
forward to to running the push-and-shove
Try using wxWidgets_CONFIG_EXECUTABLE=/path/to/wx-config instead of
-DwxWidgets_ROOT_DIR=/path/to/wx. Even though FindwxWidgets.cmake
claims wxWidgets_ROOT_DIR is the way to specify a custom wxWidgets path,
I cannot get it to work either.
You could try temporarily removing you libwxgtk2.8-dev
01/10/14, 15:46, Wayne Stambaugh kirjoitti:
You could try temporarily removing you libwxgtk2.8-dev (Debian based
distros) package so the CMake will only be able find your custom
Only after starting the build from a clean directory the system
installed libwxgtk3.0-dev was found without problems
My OS X build is still broken.
I ran a quick check about wx-config, and got the result below:
Jean-Pauls-MacBook-Pro:~ jean-paullouis$ sudo find / -name wx-config
find: /dev/fd/3: Not a directory
find: /dev/fd/4: Not a directory
On 10/01/2014 07:46 AM, Wayne Stambaugh wrote:
Try using wxWidgets_CONFIG_EXECUTABLE=/path/to/wx-config instead of
-DwxWidgets_ROOT_DIR=/path/to/wx. Even though FindwxWidgets.cmake
claims wxWidgets_ROOT_DIR is the way to specify a custom wxWidgets path,
I cannot get it to work either.
You
Hi,
/opt/local/Library looks like a MacPorts installation.
You won’t be happy with that because it is missing the needed wxOverlay patches.
Further, MacPorts seems to do the Framework stuff wrong (besides wxWidgets
itself messing up the library names in OSX builds). CMake BundleUtilities as
Maybe you should try an out-of-tree build (create a separate build directory
and call cmake from there) and completely wipe out the build directory whenever
you change path or compile switches.
Sometimes some things get left behind causing problems.
Regards,
Bernhard
On 01.10.2014, at 23:11,
Hi,
either set $PATH in the shell where you build in a way that wx-config can be
found (i.e., to your wxWidgets/bin folder) or use
-DwxWidgets_CONFIG_EXECUTABLE=path/to/your/wx-config
switch with kicad (this works for me on OSX, but should also be the same for
Linux).
Regards,
Bernhard
On
well, I took the advice offered and added the wxWidgets bin directory
to the front of my PATH. I added the wxWidgets lib directory to the
front of the LD_LIBRARY_PATH.
cmake . -DwxWidgets_CONFIG_EXECUTABLE=/home/jfm/wx/bin/wx-config
cmake .
On 9/30/2014 4:57 PM, inkblotter wrote:
well, I took the advice offered and added the wxWidgets bin directory
to the front of my PATH. I added the wxWidgets lib directory to the
front of the LD_LIBRARY_PATH.
cmake . -DwxWidgets_CONFIG_EXECUTABLE=/home/jfm/wx/bin/wx-config
cmake .
Wayne,
I tried at r5159 and got exactly the same errors as I wrote about below.
Is it possible to have wxWidgets somewhere in the HOME directory tree?
If so, is cmake . -DwxWidgets_ROOT_DIR=/home/jfm/wx ...
the right command to use on Linux to find my compiled wxWidgets?
I wish I knew more
Why don’t you try
-DwxWidgets_CONFIG_EXECUTABLE=path/to/your/wx-config
as I suggested?
This works for me all the time.
Regards,
Bernhard
On 01.10.2014, at 04:16, inkblotter inkbot...@gmail.com wrote:
Wayne,
I tried at r5159 and got exactly the same errors as I wrote about below.
I have very recently built a new 64-bit linux system, with a new GPU.
Of course, I wanted to build kicad on this new system.
I have installed cuda and built wxWidgets 3.0.1 and I really look
forward to to running the push-and-shove router.
But I never make it past the wxWidgets test in
13 matches
Mail list logo
