Thanks Valerio.
> probably you mean install instead of uninstall
Actually, I had MSYS2 already installed, so I uninstalled it and I
followed your instructions verbatim. Your step 9 "optional dev
packages" does not appear to be optional. Gettext appears to be
required to build gerbv. Also, pacman couldn't find
"intltool-0.51.0-2", but it was able to install "intltool" instead.
> Before run the script, remember to set in first 4 lines with:
> - 32 or 64 bit setting
> and the three paths:
> - MSYS2 root directory
> - sources/build root directory
> - sandbox directory
Which script are you talking about?
Once I had a working MSYS2, I opened a Mingw32 window and I issued the
following commands:
$ cd /c/temp # gerbv sandbox location on disk
$ git clone git://git.geda-project.org/gerbv.git
$ cd gerbv
$ sh autogen.sh
$ ./configure --disable-update-desktop-database
$ make
$ make install
(Configure fails to find "update-desktop-database", so it must be
disabled. Apparently Sergey always builds with it disabled.)
I could not run gerbv until I ran "make install". The program runs
equally as well from a Windows shortcut, a Windows command prompt and a
Mingw32 shell. However, when running from Mingw32, GTK complains about
being unable to release a display context when gerbv exits.
"make install" places gerbv.exe in the /msys64/mingw32/bin directory
with 200 Mbytes of other files. How did you extract the program and
necessary DLL's to generate your distribution archives?
-L
On 2017-03-03 12:08, Valerio Messina wrote:
> On 03/03/2017 18:23, Linda Huxley wrote:
>> I'll also uninstall MSYS2 and try your script from scratch
>
> probably you mean install instead of uninstall
>
>
>> any further instructions for completing the build (so that everything
>> is in one place)?
>
> once you have a working MSYS2 with all dependencies, build instructions
> are the same as Linux (autogen, configure, make).
>
> Before run the script, remember to set in first 4 lines with:
> - 32 or 64 bit setting
> and the three paths:
> - MSYS2 root directory
> - sources/build root directory
> - sandbox directory
>
> After run the script, open a Windows command prompt, goes where you
> created the sandbox.
> Here set an empty PATH, to reduce the risk of find some dll in other
> directory used by other applications already installed in your system
> (for example I had GIMP, Evince, Gedit, others).
> The command is:
> >set PATH=
>
> enjoy,
> Valerio
>
>
------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Gerbv-devel mailing list
> Gerbv-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gerbv-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Gerbv-devel mailing list
Gerbv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gerbv-devel
