[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mingw-cross-env-list] Python as a build dependency in MXE
From: |
Rick van Rein |
Subject: |
[Mingw-cross-env-list] Python as a build dependency in MXE |
Date: |
Thu, 16 Jun 2016 20:58:24 +0200 |
User-agent: |
Postbox 3.0.11 (Macintosh/20140602) |
Hi,
I'm trying to add my quick `n' easy DER library to MXE,
https://github.com/vanrein/quick-der
It works with precompiled template files that can be included with
things like
#include <quick-der/rfc5280.h>
To precompile these templates while building Quick DER, we use an ASN.1
compiler dependent on
- the Python language
- the python-parsing package
Questions:
1. The MXE tree consistently deconfigures Python -- is there a
structural reason for that? [other than a plethora of dependencies of
course]
2. Can I expect Python to run on the build env, or should I build (and
perhaps even install) it?
3. Is there a way to download python-parsing as a secondary package to
the primary source, and use it locally?
Oh... I almost forgot... we're really happy with the robust building
framework of MXE! We use it to port our TLS Pool to Windows,
http://tlspool.arpa2.net
https://github.com/arpa2/tlspool
Thanks,
-Rick
- [Mingw-cross-env-list] Python as a build dependency in MXE,
Rick van Rein <=