Building V5 runtime and win32 api as native build on Windows

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Building V5 runtime and win32 api as native build on Windows

David Gressett-5
There are no build instructions for these How can I
build them from source as a native Windows build?

I'm doing experiments with building a MinGW gcc 7.1
that uses sjlj exceptions. I know very little about how
exceptions are done by gcc, but I expect that inconsistent
exception handling methods will cause trouble, so I'm
trying to rebuild everything I might possibly use with
my sjlj test version of gcc 7.1
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Reply | Threaded
Open this post in threaded view
|

Re: Building V5 runtime and win32 api as native build on Windows

Keith Marshall-3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 17/05/17 19:56, David Gressett wrote:
> There are no build instructions for these How can I
> build them from source as a native Windows build?

Both follow the conventional GNU paradigm:

  $ configure && make && make install

By default, configure should set prefix to /mingw; use the --prefix=...
option, if you wish to stage it elsewhere.  Besides that, there is one
wrinkle you should consider ... both source packages are interdependent,
and must both must be available (in unpacked form), in a common parent directory, before either can be built as a separate entity.

You may find it more convenient to build from a git, (or hg), clone of
the WSL repository:

  https://sourceforge.net/p/mingw/mingw-org-wsl/ci/5.0-active/tree/

This supports building both packages as an integrated entity, but does
require an additional pre-configuration step, (in the top directory of
the cloned repository tree):

  $ autoreconf -I ..

I'd also recommend building in a separate directory for each distinct
configuration you wish to create, (a subdirectory at the top level of
your source clone is fine), e.g.:

  $ mkdir build-sjlj && cd build-sjlj
  $ ../configure --prefix=<your-choice> && make && make install

should build and install both packages for you.

> I'm doing experiments with building a MinGW gcc 7.1
> that uses sjlj exceptions. I know very little about how
> exceptions are done by gcc, but I expect that inconsistent
> exception handling methods will cause trouble, so I'm
> trying to rebuild everything I might possibly use with
> my sjlj test version of gcc 7.1

That would likely be a mandatory requirement ... be sure to build it all
with that sjlj compiler itself.

- --
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJZHfXDAAoJEMCtNsY0flo/k7kP/2WoOqaV9UAmRK/6GDy9+Lkd
EhTMLd5JZ6N+KnMzaP2ueMXQCSpkh9Q3KKC9sgYdgZ5qBycwwGHyijKPgBCLaZqu
Z8EqodMPk4uM7itNcnU/c7B/j0UsZ18joKr6jdVnb3E+JQxTRcsR8iAAPgIEY2Ol
DulmTtDrjgeTaW0dCBvRD8KsoDiwMlXvVAxyXoCJHdu9dt6FDEqt9xMx5IzQOJhC
qM3t2ibxLIGgzeR0cQ1lTygT2+OYqBDYuCBdHugIPlQZaXPSMZkV46CwlGQ6W8T6
iE12dfJLNg/hM2rkEJ0FTmPBJlaTs5frQtHNPCHsxBcFENUnijBpkGK6wffvWng0
Zfc5jE2cZkP4MrP2sGdCON2qcOQmNNeLqeCPrZSNy2d/C63Mnt7RnOTusLqHQNlr
h90oh2OTOBqRql1TIuBDQGmCMLFnBI1+sf9z0WBMqTBamIIsGhi1Opzi9kI9NIWh
LTfgmAV4nw4x1lplqgamXCAYwVon3GjokHRdmHSrtrKXoQK9uKo5f4S7N/ID15+/
PcGLWGWiSzv/wO+MAXVMTCxCev2qUSro2XHR5n2RsC1ft6CyhGMtqoF9C4NYCAPF
FuqWMNQ1Lc4cdmsInVu8VZNVdWhFe7QrV8H28WyHwFD0Nk/tQgcAgnHqyuK3jBjH
Ot+IDBIP/p9hkJfibGs7
=q6/G
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Reply | Threaded
Open this post in threaded view
|

Re: Building V5 runtime and win32 api as native build on Windows

David Gressett-5
On Thursday, May 18, 2017,  Keith Marshall wrote:

>On 17/05/17 19:56, David Gressett wrote:
>> There are no build instructions for these How can I
>> build them from source as a native Windows build?

>Both follow the conventional GNU paradigm:

>  $ configure && make && make install
... snip ...
>I'd also recommend building in a separate directory for each distinct
>configuration you wish to create, (a subdirectory at the top level of
>your source clone is fine), e.g.:

>  $ mkdir build-sjlj && cd build-sjlj
>  $ ../configure --prefix=<your-choice> && make && make install

>should build and install both packages for you.

I used the integrated structure from the git repository.

Configure fails with this message:

error: cannot find install-sh, install.sh, or shtool in build-aux ".."/build-aux
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
Reply | Threaded
Open this post in threaded view
|

Re: Building V5 runtime and win32 api as native build on Windows

Keith Marshall-3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/05/17 17:56, David Gressett wrote:
> I used the integrated structure from the git repository.
>
> Configure fails with this message:
>
> error: cannot find install-sh, install.sh, or shtool in build-aux ".."/build-aux

Then you are trying to build on a (defunct) v4.x branch.  You need to
ensure that you have checked out the 5.0-active development branch:

  $ git checkout 5.0-active

OTOH, if you cloned into a mercurial working repository, you should
already be on the correct "branch"; (actually a bookmark in mercurial
parlance, this being the equivalent of a a git branch; true mercurial
branches are rather more concrete entities).  If you are unsure:

  $ hg co 5.0-active

- --
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJZH0J8AAoJEMCtNsY0flo/j5sP/2WLYybhGVJNFJf1DrVlz6XZ
9zSB9YfdpusxmRKql0tixNL7kZG4jOkPoJxngXDCSuMBwjj7nYFc2C8xI3sMP1fB
NrLst4W5BIXxv/BJVZCTo2fcBeA4A5/Rk7AEB+Ul234IU3umbjd97Wr69FHyvZ8e
SQC04PLptn1Ols5VD2IdGjPf21yLjFL72RZj6+pHJD2avocGxj+3mDUYVjgpkeMh
LLGvfpXQernYVbeEdrHjkPc0bfn5rrPjhBP9pbQQJ2X+eRKqtGExIpYSQLDdjxCn
hJK+/KLmDls/BbqlRsRiecY9dS67L7iSOr76YnAkVj1KqCHsURJklm6w27XxQS8a
QNf2h21osOJymif6D5kPMr4ORxGt+K1ZBWVJmQJw9hTtsSgNJZHpdltCwDb0Js1W
/3wtUcY2HMP/LF+elgbfj7oNGSK8EgFQPY3IMc871E8B5FegpwAO6rRhhzK/fEN8
Bs4VVR8W9NnjN1KFYY9/afrxcWVZIuzabfIbE3GPMFNYbIlMmBJO6nsCl/h6hPxU
woRTN0GT1yzir2Kd7GTBFvItJY4rS4ovIen9MPFskKJL0kq6oMRBNXr4rwY5nbbd
7fqk4B2q9sxR3GHaagQzQKyZ0A4eU8/RwdDO3JRVpfuN6k5ZjwLd3J8TnUU/sbcz
TIQSgsFJkEX/z4EJMSIw
=wsz8
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
MinGW-dvlpr mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr