LOL, well I'm not entirely convinced it was a problem with Vista. I'm not quite sure when the path was supposed to be set to the msys/1.0/bin directory (COMPILING.txt does not explicitly address it) but perhaps I did a step incorrectly. Now that the path is set, cmake does its job just fine and I can generate makefiles and compile kicad.
In any event, I learned a lot about wxWidgets and cmake and some other tools kicad uses that I didn't know existed before yesterday, so its not all bad! :) Thanks for all the help! --- In [email protected], Donald H Locker <dhloc...@...> wrote: > > You poor bkanobe. > > If you can, dump the Vista for _anything_ else. I've never liked M$ > products, but that was the absolute worst (right up there with Word and > "Excel" 2007.) Crash, hang, crash, _SLOW_, unreliable, incompatible with > almost everything - even stuff supposedly written for it. Dump it. Even try > (what's it called) Windows 7? Beta - far better. Not very good but better > than Vista. > > Donald. > > ----- Original Message ----- > From: "bkanobe" <bkan...@...> > To: [email protected] > Sent: Monday, August 10, 2009 8:36:56 AM GMT -05:00 US/Canada Eastern > Subject: [kicad-users] Re: cmake and wxwidgets > > That was actually the first thing that I did, which did not work for the same > reason (cmake could not seem to locate wxwidget.) So I tried the > --prefix...just to try something. > > Otherwise, nothing so far has worked. > > BTW, I'm doing this on Windows Vista (cringe at will) and I don't know if > this makes a difference or not compared to XP. > > I've been trying to read up on cmake so see how the find_package() function > works. So far, more confused than ever! > > > > --- In [email protected], Brian Sidebotham <brian.sidebotham@> > wrote: > > > > > ----- Original Message ----- > > > From: "bkanobe" <bkanobe@> > > > To: [email protected] > > > Sent: Monday, August 10, 2009 7:45:42 AM (GMT-0500) Auto-Detected > > > Subject: [kicad-users] Re: cmake and wxwidgets > > > > > > It certainly would appear so: > > > > > > C:\msys\1.0\local\wxMSW-2.8.10>dir > > > Â Volume in drive C has no label. > > > Â Volume Serial Number is D04E-AB3B > > > > > > Â Directory of C:\msys\1.0\local\wxMSW-2.8.10 > > > > > > 08/10/2009 Â 05:23 PM Â Â <DIR> Â Â Â Â Â . > > > 08/10/2009 Â 05:23 PM Â Â <DIR> Â Â Â Â Â .. > > > 08/10/2009 Â 07:37 PM Â Â <DIR> Â Â Â Â Â bin > > > 08/10/2009 Â 05:23 PM Â Â <DIR> Â Â Â Â Â include > > > 08/10/2009 Â 07:37 PM Â Â <DIR> Â Â Â Â Â lib > > > 08/10/2009 Â 05:23 PM Â Â <DIR> Â Â Â Â Â share > > > Â Â Â Â Â Â Â 0 File(s) Â Â Â Â Â Â Â 0 bytes > > > Â Â Â Â Â Â Â 6 Dir(s) Â 339,789,967,360 bytes free > > > > > > I eventually used the "--prefix=C:\msys\1.0\local\wxMSW-2.8.10" option > > > with configure, since the first time I configured and make (installed) > > > the wxwigets it didn't seem to install them in a separate directory, as > > > the COMPILING.txt implied. Â Rather, I think it was installed in the > > > /usr/local/bin and /lib directories (and cmake could not find them there > > > either.) So I added the --prefix so it would install in a specific place > > > that I was certain of, and included that location in the > > > -DwxWidgets_ROOT_DIR option of cmake. > > > > > > I hope that makes sense. > > > > > > Anyway, I'll keep plugging away. Â :( > > > > Normally, if you do not include a --prefix option to wxWdigets on > > windows, it will install to /usr/local under MSYS and this is what you > > should pass to cmake. i.e. cmake -G "MSYS Makefiles" > > -DCMAKE_BUILD_TYPE=Release -DwxWidgets_ROOT_DIR=/usr/local ../.../ > > > > I did this on a fresh machine yesterday so I know this is the case. > > > > When using MSYS you should "think" you are in the linux world. Stay > > away from c:\ type paths. It is likely the path structure you've given > > that is mucking up cmake. You can instead try passing > > -DwxWidgets_ROOT_DIR=/usr/local/wxMSW-2.8.10 and see if that gets you > > any luck. > > > > With the boost libraries, you'll need to unzip the boost libraries > > into a directory called "C:\Program Files\Boost". To find boost, cmake > > only looks in a few certain directories on windows. > > > > Best Regards, > > > > Brian. > > >
