Re: mgwport and multiple builds
On 2/3/2012 8:35 PM, Chris Sutcliffe wrote:
> I'm trying to package gdb 7.4 using mgwport and I'm at a bit of loss
> as to how I package it with 2 different builds (i.e. the python build
> and the non-python build). Any idea how I could handle this? Do I
> need to break it into 2 packages (i.e. gdb and gdb-python)?
No, neither cygport nor mgwport directly support building multiple
variants as part of the same package. You can 'kludge' it by chaining
multiple cofigure/make/make-clean sequences as part of src_compile(),
but that has obvious problems.
It's probably best to split into two completely separate packages, with
their own -src tarball. The only real cost for this is the additional
-src element to upload.
I assume this is for mingw32-gdb and mingw32-gdb-python. As we don't
have a mingw32-python (nor, for that matter, an msys-python), which
python implementation would mingw32-gdb-python depend on, and how would
it "find" it? ActiveState python + ${PYTHON} variable, or simple
${PATH} search, or what?
--
Chuck
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
(Continue reading)