~brad-fie/fiecac/pythonnet : changes

~brad-fie/fiecac/pythonnet » Changes from revision 109

From Revision 109 to 90

Rev	Summary	Authors	Date
109	# BUGFIX: Accommodate new output path (x86 vs. x64) # # BUGFIX: Accommodate new output path (x86 vs. x64) #	barton_c	11 years ago
108	# Move DEBUG_PRINT to the Properties->Build page of the Debu... # Move DEBUG_PRINT to the Properties->Build page of the DebugWin Configuration. #	barton_c	11 years ago
107	# FIXED: .sln and .csproj file configurations x86/x64 Mono/W... # FIXED: .sln and .csproj file configurations x86/x64 Mono/Win Debug/Release all reflected throughout # # Added Conditional Reference <Choose> <When> elements to Python.Runtime.csproj => building for Mono on Windows # # Added Required reference assemblies => building for Mono on Windows # # R# Cleanup on pyimport.cs # # Remove reference to the Python.Runtime project from Console.csproj # # BUGFIX: TARGET_PLATFORM==x86 in buildclrmodule.bat #	barton_c	11 years ago
106	Of course, for the previous to work, you'll be needing the p... Of course, for the previous to work, you'll be needing the project files to go with... But we don't need another copy of that signing key laying around.	barton_c	11 years ago
105	# Solution Configurations for each VS and MD - We'll release... # Solution Configurations for each VS and MD - We'll release x86 and x64 binaries separately. # MonoDevelop will now share the solution and project files with Visual Studio quite nicely. In fact, MD refers to .mds files as MD 1.x Solution Files. Separate configs supports different character widths on each OS platform. Platform specific settings are due, in part, to the introduction of DllExport's requirement (which actually only applies on Windows) Hmmm... Perhaps the Linux guy will want to revert to Any CPU #	barton_c	11 years ago
104	# NUnit issues begin to resolve themselves (amazing, really)... # NUnit issues begin to resolve themselves (amazing, really) since MD supports NuGet now, just grab NUnit and add it to /packages/. Honestly, though, I did have to trick NuGet into giving me the UnmanagedExport update.	barton_c	11 years ago
103	# Visual Studio 2010 .NET 4.0 (with a little ReSharper throw... # Visual Studio 2010 .NET 4.0 (with a little ReSharper thrown in) # # The new C# clrmodule depends on RGiesecke.DllExport in new pythonnet/packages directory which was import via NuGet # # The signing key finally landed in the correct directory # # Not sure why the console/Console.csproj referenced Python.Test # # Python.Runtime Assembly version bumped to 4.0.0.1 # # Tool and Framework versions all bumped for .NET 4.0 # # [Obsolete?] buildclrmodule.bat got a tiny note after cli research on clrmodule.il # # EmbeddingTest remains in flux while issues with nUnit (version bump) get ironed out #	barton_c	11 years ago
102	NOTE: All this maintenance led to the soon-to-be-committed D... NOTE: All this maintenance led to the soon-to-be-committed DllExport enable module: # Cleanup after much ildasm and research: .fixup, .vtentry, etc. are all handled by the build system since late .NET 2.0. So there's no need to import the platform any longer. There's no fear of conflict with Linux - Mono needs a completely different mechanism (clr.so) to get the "Late Binding" ball rolling. # # There is a big chunk of notes taken regarding my findings # # .ver 4:0:0:1 matches Python.Runtime's version # # I've turned on options for USE_PYTHON_RUNTIME_VERSION and USE_PYTHON_RUNTIME_PUBLIC_KEY_TOKEN # ## The signing key was generated on Linux without any certification (to satisfy the build script) ##	barton_c	11 years ago
101	# Add Signing Key # # Add Signing Key #	barton_c	11 years ago
100	Added new usage on "Overloads" Added new usage on "Overloads"	barton_c	11 years ago
99	Update links which were broken since SF upgrade Update links which were broken since SF upgrade	barton_c	11 years ago
98	# Add Signing Key # # Add Signing Key #	barton_c	11 years ago
97	# VS 2008 => 2010 project files (remain compatible with 2008... # VS 2008 => 2010 project files (remain compatible with 2008) #	barton_c	11 years ago
96	# Update notes on "failed" tests " # Update notes on "failed" tests "	barton_c	11 years ago
95	# Build using %windir%\Microsoft.NET\Framework\v4.0.30319\il... # Build using %windir%\Microsoft.NET\Framework\v4.0.30319\ilasm # # Remove duplicate script (perhaps intended to build alternate clr versions???) # # Windows clr.pyc now header indicates clr version 4.0 # # PYTHON26 => PYTHON27 # # InitExt() now keeps pace with "CLR" deprecation warnings # # PythonException doesn't seem to pick up the TraceBack - Test for null TB in Dispose() # # Clean up formatting on Runtime.Decref() for clear picture of intent. #	barton_c	11 years ago
94	# VS solution files for 2008 and 2010 # # VS solution files for 2008 and 2010 #	barton_c	11 years ago
93	# Preserve VS 2005 sln # # Preserve VS 2005 sln #	barton_c	11 years ago
92	# Add modified python-clear.ico # # Add modified python-clear.ico # # Add sourceforge-logo.png # # assemblyinfo.cs added automatically # # Set Framework version to 4.0 #	barton_c	11 years ago
91	Add required import clr and some diagnostics Add required import clr and some diagnostics	barton_c	11 years ago
90	# Apply Alexey's Exception memory leak patch # # Apply Alexey's Exception memory leak patch # # Apply Alexey's PythonException AquireLock patch #	Barton_c	12 years ago

Older »