I've created a bug with a sample project that reproduces the issue.
https://bugzilla.xamarin.com/show_bug.cgi?id=5146
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Linking-Problem-tp5696452p5709860.html
Sent from the Mono for Android mailing list archive at Nabbl
The MonoGame project is set to be an application instead of a library?
Interesting. I'll check that out when I get home. Thanks for the tip.
Sly
On 18 May 2012 09:49, Jonathan Pobst wrote:
> You might want to look at what I wrote here:
>
> https://bugzilla.xamarin.com/**show_bug.cgi?id=5146<
You might want to look at what I wrote here:
https://bugzilla.xamarin.com/show_bug.cgi?id=5146
If it's the same issue, I don't think it has anything to do with
implicit references.
Jonathan
On 5/17/2012 5:36 PM, Konaju Games (Dev) wrote:
Seeing the other threads about this linking issue, a
On May 17, 2012, at 6:36 PM, Konaju Games (Dev) wrote:
> could we expect an update for MfA to go back to implicit linking?
Can we? Most likely. When? Probably _not_ the next release; we'll see...
> This linker issue is a blocker for my work on MonoGame as even adding the
> reference to Lidgren t
Seeing the other threads about this linking issue, and your decision to
exercise your disclaimer clause to now be in favour of implicit linking,
could we expect an update for MfA to go back to implicit linking? This
linker issue is a blocker for my work on MonoGame as even adding the
reference to
On May 17, 2012, at 9:20 AM, Konaju Games (Dev) wrote:
> >> We don't implicitly include additional assemblies.
> We have never had to explicitly reference the Lidgren.Network.Android project
> from our startup project before. Is that a new requirement in MfA 4.2?
I had thought that we always had
I've just come across this now as well, trying to update the MonoGame
project for use with MfA 4.2.1 in VS2010. It links with Lidgren correctly
in library projects that reference MonoGame.Framework.Android in the same
solution, but not the executable project.
>> We don't implicitly include additi
On May 16, 2012, at 12:11 AM, zdman wrote:
> Alright. Well, like I said before, it gives the same error if I add a project
> reference to the lidgren project.
Could you please file a bug and attach the project. This seems rather odd.
Thanks,
- Jon
__
Alright. Well, like I said before, it gives the same error if I add a project
reference to the lidgren project.
{565129E0-4EE5-4F6F-B403-C3484C9740BE}
Lidgren.Network.Android
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Linking-Problem-tp569645
On May 14, 2012, at 1:49 PM, zdman wrote:
> The project(udderchaosmonodroid) throwing the error does not reference
> Lidgren.Network.Android. It references MonoGame.Framework.Android which
> references Lidgren.Network.Android. udderchaosmonodroid does not use
> lidgren.network.android or any o
The project(udderchaosmonodroid) throwing the error does not reference
Lidgren.Network.Android. It references MonoGame.Framework.Android which
references Lidgren.Network.Android. udderchaosmonodroid does not use
lidgren.network.android or any of the methods in monogame that use it. It
was workin
On May 11, 2012, at 7:30 PM, zdman wrote:
> I updated to 4.2.0 and ran into an issue with System.Drawing.Size being
> defined in Mono.Android and OpenTK.
It shouldn't only be in Mono.Android.dll, not OpenTK.dll or OpenTK-1.0.dll in
4.2.0 and later.
> With 4.2.1, I'm still getting the same refer
I updated to 4.2.0 and ran into an issue with System.Drawing.Size being
defined in Mono.Android and OpenTK. But, it looks like 4.2.1 fixed that
issue. With 4.2.1, I'm still getting the same reference issue I posted
about before.
--
View this message in context:
http://mono-for-android.1047100.n
Could you please try the latest 4.2.0 alpha? (available in Alpha channel)
It contains some fix for linking issue.
Atsushi Eno
On 2012/05/09 13:48, zdman wrote:
I think there's a linking problem with 4.1.1. It was working with 4.0.6 but
upon upgrading and after fixing all the syntax changes, th
I think there's a linking problem with 4.1.1. It was working with 4.0.6 but
upon upgrading and after fixing all the syntax changes, the deployed project
is throwing this error on compile. The project doesn't use this and even if
I add that project as a reference, it still fails.
Error 49
ings etc), so I thought it was safer to just leave it as-is.
Sorry I can't be of more help!
Andy
-Original Message-
From: monodroid-boun...@lists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Matt
Sent: 27 April 2012 17:38
To: monodroid@lists.ximian.com
Subjec
Andy,
So it looks like you are only obfuscating your libraries and not the main
application? The problem I have is obfuscating the main application. My
process (which doesn't work for obfuscating the main app), goes something
like this:
ComponentBuild (libraries)
CopyComponentFiles (copy files so
(jar signer and zipalign)
...
Cheers,
Andy
-Original Message-
From: monodroid-boun...@lists.ximian.com
[mailto:monodroid-boun...@lists.ximian.com] On Behalf Of Matt
Sent: 27 April 2012 17:10
To: monodroid@lists.ximian.com
Subject: Re: [mono-android] Linking problem with obfuscated assembly
Andy ,
Thanks for your help. The obfuscator that I am using (9-rays) has an option
to emit alphabetic type names, which I would assume are all valid Java
names. I tried using this option and it didn't help. Do you know of any way
to get more useful debug information from the M4A linker? Based on t
alf Of Matt
Sent: 26 April 2012 03:29
To: monodroid@lists.ximian.com
Subject: [mono-android] Linking problem with obfuscated assembly
I am having a couple different problems linking my assemblies after they are
obfuscated. I have two library assemblies and the main application assembly,
all of which a
I am having a couple different problems linking my assemblies after they are
obfuscated. I have two library assemblies and the main application assembly,
all of which are compiled for Mono for Android. If I obfuscate only the
first library assembly, I am able to link and build my apk without any
pr
In case anyone else comes across this issue - this is how I solved it.
I was using Resco's Mobile Forms Studio to generate some of the activities.
Removing the MobileFormsStudio.AndStyleManager.dll from the Project
references allowed me deploy successfully with SDK linking enabled.
(C:\Program F
On Feb 15, 2012, at 4:38 AM, devbuzz wrote:
> I need to zip it up and email as attachment.
You should be able to file a bug at bugzilla.xamarin.com and mark the
attachment as private.
> I use Resco controls for MfA - do you guys have a license/not sure if this is
> an issue?
We don't have a li
Hi Atsushi,
Thanks for the reply. No problem to send you the source.
Could you email me at de...@devbuzz.com so I can get your email address?
I need to zip it up and email as attachment.
I use Resco controls for MfA - do you guys have a license/not sure if this
is an issue?
The "hidden email"
Could you please give us your code (hopefully via bugzilla private or
public comment, or private email to atsu...@xamarin.com) so that I can
investigate the issue?
Thanks,
Atsushi Eno
devbuzz wrote:
I'm getting an error when I try to deploy a solution using Linking.
With linking disabled eve
I'm getting an error when I try to deploy a solution using Linking.
With linking disabled every things works fine but the apk is large ~20MB.
I set Linking = Sdk Assemblies Only
(User Shared Runtime is unchecked.)
The error seems to relate to Android.Widget.TextView?
Error Text:
Packaging Fail
26 matches
Mail list logo
