[Python.NET] Several patches to improve compilation with Mono
barton at BCDesignsWell.com
Fri Sep 2 08:52:02 CEST 2011
Nice to know that you're still around.
All these build tool issues make me a little crazy. My background on on
Windows, but I'm trying to divorce myself from the M$ platform.
(I just adore my Fedora system) But things are still a little new to me
on the Linux side.
Now that I'm all set up with side-by-side build, and can serve my own
SVN repo locally, I'll pull together all the contributions and finally
commit to the VS2008 that I've been building with.
Interestingly, the github version has fully integrate nUnit integration
(turns out a bit of this has leaked onto the trunk and broke my
TestModule module). It makes me wonder if it's worth committing to the
On 8/31/2011 8:15 AM, Philip Lorenz wrote:
> Hi Barton,
> On 08/29/2011 07:44 AM, Barton wrote:
>> So if git is producing your udiff files, does that mean that you are
>> actually pulling from the clone that's on github?
> I used the GIT-SVN bridge in order to create those patches. But may be
> something was wrong with my working copy.
>> I (sort or) like the clrmodule_make.il input file name, but what to do
>> for Windows folks?
> I haven't personally used the Makefile on Windows based systems (I
> always built Python.NET using the bundled Visual Studio Solution file).
> I don't know how exactly the Makefile would be invoked on Windows (is it
> a nmake compatible syntax?). A way to solve the issue could be to
> replace the "cp oldmodule.il clrmodule_make.il" statement in the else
> case with "copy clrmodule.il clrmodule_make.il".
More information about the PythonDotNet