Broken compile fixes#2
Conversation
…as causing build error.
- Bumped target frameworks to 4.0 to work with gtk-sharp 2.12 - Set all projects to output their binary into common "..\bin" solution directory. - Set CPU to x86 for compatibility with gtk-sharp 2.12 on 64-bit systems
…eapshot" to align with current mono versions. Added instructions for compiling and running on Windows.
|
This PR needs to be tested on a Mac. @migueldeicaza has indicated to me that it may potentially break the build on Mac. |
|
@BrandonLWhite why not create a configuration specifically for Windows and call it DebugWin32 or something like that. That would ensure not breaking Mac. |
|
+1. |
|
Command line HeapShot was unchecked in build configuration. When I switch it on the errors occurs. The ObjectMapReader object has changed interface and compilation fails. The information about removing "." very useful - the information given by VS2013 is confusing. I am trying to compile HeapShot to use it under Debian (X-less) server to grab data from application working as daemon under mono. Is there still ready to help the author of the changes made to ObjectMapReader? |
|
@czaban Select the appropriate target (x86). It works for me |
|
On 2015-10-12 09:33, Cybermaxs wrote:
|
Hi, I ran into multiple issues compiling and running heap-shot on Windows x64 using VS2012. I got it working and would like to contribute these changes back upstream.