cosmos plugin on monodevelop (gnu/linux)

Aug 3, 2011 at 8:48 AM

hello all i will run the cosmos plugin on my ubnutu laptop i have only monodevelop and mono

how to run this (native) on my laptop

Aug 3, 2011 at 3:35 PM

Wine???

Developer
Aug 3, 2011 at 5:51 PM

Currently Wine is the only option, because the build process is hard-coded to use windows native files (Nasm, and makeisofs), although if we made a few modifications, we could use the ones installed on the system.


@Devs working in this area: We could use the ones installed on the system if we tried to resolve to path first, then used the one included in the install, because this would find the native one on linux, and still allow it to work on windows. Also could do a simple check of OS (Look into the System.Environment class) if you want to avoid trying to resolve on path when on windows.

Coordinator
Aug 3, 2011 at 5:58 PM
using the right nasm and ld executables is the easy part by far. our compiler needs to run on mono as well (which might actually work at the moment), and the mono-specific assemblies need to be plugged, which is something we dont want for now, as it's a huge amount of work..


On Wed, Aug 3, 2011 at 6:51 PM, blah38621 <notifications@codeplex.com> wrote:

From: blah38621

Currently Wine is the only option, because the build process is hard-coded to use windows native files (Nasm, and makeisofs), although if we made a few modifications, we could use the ones installed on the system.


@Devs working in this area: We could use the ones installed on the system if we tried to resolve to path first, then used the one included in the install, because this would find the native one on linux, and still allow it to work on windows. Also could do a simple check of OS (Look into the System.Environment class) if you want to avoid trying to resolve on path when on windows.

Read the full discussion online.

To add a post to this discussion, reply to this email (Cosmos@discussions.codeplex.com)

To start a new discussion for this project, email Cosmos@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Aug 3, 2011 at 9:24 PM

no wine is not workiking then you must be have visual studio!

Developer
Aug 4, 2011 at 12:45 AM

You still have to Create the plugin for MonoDevelop before you could do so, but there is no reason (other than plugs, and issues with resolving overloads), that running each of the steps manually shouldn't work.

Coordinator
Aug 4, 2011 at 10:00 AM
blah: so you say it probably works??

definitely not: we tries it before, but disabled it as the differences were too big...


On Thu, Aug 4, 2011 at 1:45 AM, blah38621 <notifications@codeplex.com> wrote:

From: blah38621

You still have to Create the plugin for MonoDevelop before you could do so, but there is no reason (other than plugs, and issues with resolving overloads), that running each of the steps manually shouldn't work.

Read the full discussion online.

To add a post to this discussion, reply to this email (Cosmos@discussions.codeplex.com)

To start a new discussion for this project, email Cosmos@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Developer
Aug 4, 2011 at 7:07 PM

Did you try compiling it against Mono in the first place? Because there are multiple places where overloads can't be fully resolved, where-as they can be when compiled against Microsoft .Net. One such place is System.IO.Path, as there are a few methods in there that can't be properly resolved on Mono.

Coordinator
Aug 5, 2011 at 9:04 AM
we had it working on mono, but the problem was with the plugs.

That being said, it was in our VS2008 era, so now some things might not work. sure, but if it's stuff like System.IO.Path, it's relatively easy to contribute that to mono....


On Thu, Aug 4, 2011 at 8:07 PM, blah38621 <notifications@codeplex.com> wrote:

From: blah38621

Did you try compiling it against Mono in the first place? Because there are multiple places where overloads can't be fully resolved, where-as they can be when compiled against Microsoft .Net. One such place is System.IO.Path, as there are a few methods in there that can't be properly resolved on Mono.

Read the full discussion online.

To add a post to this discussion, reply to this email (Cosmos@discussions.codeplex.com)

To start a new discussion for this project, email Cosmos@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com