Skip to content
This repository was archived by the owner on Dec 15, 2020. It is now read-only.

Conversation

@BrandonLWhite
Copy link

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.

- 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.
@BrandonLWhite
Copy link
Author

This PR needs to be tested on a Mac. @migueldeicaza has indicated to me that it may potentially break the build on Mac.

@Therzok
Copy link
Contributor

Therzok commented Sep 17, 2014

@BrandonLWhite why not create a configuration specifically for Windows and call it DebugWin32 or something like that. That would ensure not breaking Mac.

@cybermaxs
Copy link

+1.
Very useful with Xamarin.

@czaban
Copy link

czaban commented Oct 10, 2015

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?

@cybermaxs
Copy link

@czaban Select the appropriate target (x86). It works for me

@czaban
Copy link

czaban commented Oct 12, 2015

On 2015-10-12 09:33, Cybermaxs wrote:

@czaban https://github.com/czaban Select the appropriate target
(x86). It works for me


Reply to this email directly or view it on GitHub
#2 (comment).

By default the command line tool HeapSize is switched off in the x86
configuration - the point is I need to use command line tool.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants