Re: [Ikvm-developers] Using MonoLinker on ikvmc generated assembly

[Jeroen F. <je...@su...>]

Hi Marius,

Thanks. If you'd like to write a blog about this, I'd be happy to post it to weblog.ikvm.net. Alternatively, if you send me the raw information I'll see what I can cook from it.

Regards,
Jeroen
________________________________________
From: Marius Ungureanu <mar...@xa...>
Sent: Thursday, April 3, 2014 5:58 AM
To: Jeroen Frijters
Cc: ikv...@li...
Subject: Re: [Ikvm-developers] Using MonoLinker on ikvmc generated assembly

Hey Jeroen,

Thanks for the help. I managed to get all of this working flawlessly. :D

Luckily, the test suite they had covered all locales. So I didn't have
to handle it manually.

If you want me to send you information on all I did to get it work,
please tell. This would be an useful blog post.

Best regards,
Marius

On Wed, Apr 2, 2014 at 10:35 AM, Jeroen Frijters <je...@su...> wrote:
> Yes, that's probably a good place to start.
>
> Regards,
> Jeroen
> ________________________________________
> From: Marius Ungureanu <mar...@xa...>
> Sent: Tuesday, April 1, 2014 6:09 PM
> To: Jeroen Frijters; ikv...@li...
> Subject: Re: [Ikvm-developers] Using MonoLinker on ikvmc generated assembly
>
> So basically, I the lowest level thing I should hook on is
> ClassLoaderWrapper.cs : RegisterInitiatingLoaderCritical, right? Seems
> to be called from most loading parts.
>
> If there's some better place to cover it all, please tell.
>
> Thanks,
> Marius
>
> On Mon, Mar 31, 2014 at 5:20 PM, Marius Ungureanu
> <mar...@xa...> wrote:
>> Hey Jeroen,
>>
>> Thanks. I'll try this solution. I'll resurrect the thread if I stumble upon any other questions.
>>
>> Jeroen Frijters <je...@su...> wrote:
>>
>>>Hi Marius,
>>>
>>>I think that most of the reflection problems come from the Java code, not the IKVM runtime itself.
>>>
>>>I've been thinking about this and currently my best direction for solving this would be to have a modified runtime that logs all reflection usage and a tool to post process the log into an xml file for the linker.
>>>
>>>I haven't had time to actually try this though.
>>>
>>>It also wouldn't get you all the way there, because some reflection is based on environmental factors (e.g. the current culture), but I'm guessing these are limited and can be handled manually (i.e. hard coded in the tool).
>>>
>>>Regards,
>>>Jeroen
>>>
>>>> -----Original Message-----
>>>> From: Marius Ungureanu [mailto:mar...@xa...]
>>>> Sent: Monday, March 31, 2014 15:23
>>>> To: ikv...@li...
>>>> Subject: [Ikvm-developers] Using MonoLinker on ikvmc generated assembly
>>>>
>>>> Hey guys!
>>>>
>>>> I'm attempting to use MonoLinker on a jar that I generated to a dll.
>>>> The problem is, they're stripped out when I use '-a' which does static
>>>> checking for used types.
>>>>
>>>> I'm wondering if there is a pattern to the dynamically loaded classes
>>>> and their classloaders so I can add them to an xml file which will force
>>>> monolinker to keep them. Or if this data is kept anywhere, such as
>>>> Attributes.
>>>>
>>>> Thanks!
>>>> Marius
>>>>
>>>> ------------------------------------------------------------------------
>>>> ------
>>>> _______________________________________________
>>>> Ikvm-developers mailing list
>>>> Ikv...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/ikvm-developers