kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxxxx>]

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
typical linux file system layout.  You should be able take the contents
of the psuedo install path along with all of the dependency libraries
and create a nsis installer.  There is an NSIS script in the installers/
folder to create the windows installer.  I'm not sure if it includes
pulling in all of the necessary library dependencies so it may have to
modified but it should not be very difficult.  We could always just
create msys2 packages which would be really easy.  Download and install
msys2 (both 64 and 32 bit versions), install the packages required build
kicad, run makepkg-mingw to build the packages, then push the packages
to a public server along with an md5sum.  User's who have msys2
installed can just grab the latest package file and use pacman to
install it.  This is probably the path of least resistance.

Wayne

On 10/25/2014 12:27 PM, Adam Wolf wrote:
> 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
> make it cross platform.  On the other hand, if you're not, I'll just use
> my script.
> 
> Adam Wolf
> Cofounder and Engineer
> W&L
> 
> On Sat, Oct 25, 2014 at 11:22 AM, Wayne Stambaugh
> <stambaughw@xxxxxxxxxxx <mailto:stambaughw@xxxxxxxxxxx>> 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 the msys/mingw file structure.  The msys/mingw file
>     structure is the same as linux except for the library binaries which get
>     installed in the bin/ folder in order for the executable to be able to
>     find the libraries.  I propose that we change our windows install paths
>     to be the same as linux except for the kiface libraries.  Our path
>     search code can be simplified since windows and linux have the same
>     relative install paths.  Our windows install would look like
> 
>     # Path for executable and shared objects.
>     ${CMAKE_INSTALL_PREFIX}/bin
> 
>     # Path for documentation.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/doc
> 
>     # Path for demo projects.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/demos
> 
>     # Path for project templates.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/templates
> 
>     # Path for component libraries.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/library
> 
>     # Path for plugings.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/plugins
> 
>     # Path for data files.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad
> 
>     # Path for footprint library files when no GitHub.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/modules
> 
>     # Path for 3D model libraries.
>     ${CMAKE_INSTALL_PREFIX}/share/kicad/share/modules/packages3D
> 
>     If no one objects to these changes, I will update our install paths
>     accordingly and submit the kicad package build file to the msys2
>     project.  Hopefully, soon you will be able to install msys2 and install
>     kicad by running the `pacman -S`.
> 
>     Thanks,
> 
>     Wayne
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     More help   : https://help.launchpad.net/ListHelp
> 
>