kicad-developers team mailing list archive

[Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx>]

No problem.  It's better to do it this way.

Adam Wolf

On Wed, Apr 8, 2015 at 12:28 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
wrote:

> I just committed a fix for this in r5585.  You can now specify the
> install path by defining -DDEFAULT_INSTALL_PATH=/default/install/path
> when running CMake.  If you do not define DEFAULT_INSTALL_PATH, it will
> be set the CMAKE_INSTALL_PREFIX.  When building and installing from
> source, do not define DEFAULT_INSTALL_PATH unless you have a specific
> reason for doing so.  If you are building packages where
> CMAKE_INSTALL_PREFIX is a path other than the final install destination,
> then you should define DEFAULT_INSTALL_PATH accordingly.  OSX bundle
> builders will need to set DEFAULT_INSTALL_PATH=/Library/Application
> Support/kicad to maintain the previous behavior (Sorry Adam).  This was
> done to simplify the default path configuration code in both the CMake
> and source files.  Just to reiterate, this will not solve the problem
> when the user changes the default install path in windows.
>
> On 4/5/2015 1:13 PM, Nick Østergaard wrote:
> > I am not quite sure what I should do to fix the issue.
> >
> > Is it possible for some devs who is on windows to help fixing this issue?
> >
> > 2015-04-03 10:48 GMT+02:00 Bernhard Stegmaier <stegmaier@xxxxxxxxxxxxx>:
> >> Hi,
> >>
> >> as far as I remember we discussed this for OS X with Wayne some while
> back…
> >> On OS X Wayne just added some special treatment to set the paths to
> fixed
> >> paths (which is OK for OS X) instead of using some compile-time values
> from
> >> CMake.
> >>
> >> Look around
> >>   https://lists.launchpad.net/kicad-developers/msg16597.html
> >>
> >>
> >> Regards,
> >> Bernhard
> >>
> >>
> >> On 03 Apr 2015, at 01:08, Nick Østergaard <oe.nick@xxxxxxxxx> wrote:
> >>
> >> Hello
> >>
> >> As I am trying to make the windows installer work, I have found that
> >> the KISYSMOD variable it not set properly on the userend.
> >>
> >> When someone else installs it, it will be as the build host set it. For
> >> example:
> >>
> >>
> C:\msys64\home\username\MINGW-packages\mingw-w64-kicad-git\pkg\mingw-w64-x86_64-kicad-git\mingw64\share\kicad\modules
> >>
> >> What can I do to handle this, such that it is not set to that path,
> >> but rather a path that makes sense. And how should this be handled if
> >> the libraries are split into another installer?
> >>
> >> I guess Adam had similar trouble with his OS X installer, but I don't
> >> rember nor can I find information relating to this and a solution. So
> >> I would be greatfull if anyone can point me to a solution.
> >>
> >> Regards
> >> Nick Østergaard
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >>
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>