Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Would be nice to have a portable library #146

Closed
lostmsu opened this issue Nov 30, 2013 · 10 comments
Closed

Would be nice to have a portable library #146

lostmsu opened this issue Nov 30, 2013 · 10 comments

Comments

@lostmsu
Copy link
Contributor

lostmsu commented Nov 30, 2013

Otherwise any client of Cecil has to stick to compile-time directives to implement portability

@jbevain
Copy link
Owner

jbevain commented Jan 21, 2014

Agreed. It would be nice to have a PCL compatible configuration (not a new csproj).

@benpye
Copy link

benpye commented Nov 16, 2014

Has there been any progress on this goal? This is something that would also serve useful for my current project as ideally I'd use Cecil within my PCL, currently I'm having to perform the processing externally.

@jbevain
Copy link
Owner

jbevain commented Nov 17, 2014

@benpye Hey Ben,

I'm glad you pinged! I did put some work on this, and pushed it last week to the pcl branch, where you get a read only Cecil to read assemblies that work on the PCL profile.

Quite a lot of strings have to be stripped for this compile, obviously.

I was wondering it was worth merging or not.

Could you describe what is your scenario?

@benpye
Copy link

benpye commented Nov 24, 2014

Apologies for the slow response, life has been busy.

The use case for the PCL build in this case is to generate code from the assembly, eg. GLSL. This at least partially would ideally happen in a PCL with then the actual code generation in another binary. I haven't looked into getting ICSharpCode.Decompiler as a PCL yet however as that is another library that would be almost required.

@jbevain
Copy link
Owner

jbevain commented Nov 27, 2014

Hey @benpye,

No worry, quite busy here too :)

You can't load generated code with the PCL profile, so again, I'm seriously doubt the usefulness.

@benpye
Copy link

benpye commented Nov 27, 2014

The PCL will generate an AST hopefully which then platform specific code can handle. The alternative is to generate the AST in the platform code maybe using the shared projects functionality.

@rprouse
Copy link

rprouse commented May 25, 2015

@jbevian, we are considering using Cecil in NUnit 3 to help with exploring and executing tests. We were hoping for a PCL version to help target Xamarin and other platforms with a single codebase.

I haven't gone very deeply down this track, but I wanted to let you know of our intentions so we can coordinate if you decide to look at this again. I have forked the repo over to the nunit org and will play with it there. I will report back once I know more.

@jbevain
Copy link
Owner

jbevain commented May 26, 2015

@rprouse there's the pcl branch.

@rprouse
Copy link

rprouse commented May 26, 2015

@jbevain, thanks. I pulled it last night and merged latest from master. I will experiment with it in nunit tonight.

@jbevain
Copy link
Owner

jbevain commented Jun 1, 2015

Moving this discussion in #220.

@jbevain jbevain closed this as completed Jun 1, 2015
agocke pushed a commit to agocke/cecil that referenced this issue Mar 23, 2024
…110.4 (jbevain#146)

[release/8.0] Update dependencies from dotnet/arcade
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants