|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
|
|
Windows! (Yes, I said WINDOWS!)Attention Banshee-ites! I've been scarce of late - other obligations.
I won't go into the gory details but to say that I am legally obligated [1] to use Windows for the time being. What fun. VLC makes for quite a poor music manager indeed, and I will be seen dead before voluntarily using iTunes or WMP. This can mean only one thing: http://ssblack.co.nz/Winshee.jpg I got a fresh checkout at about 7pm and that was the state of things by midnight. Five hours of work ain't too bad considering that same feat took me almost a month last time [2]. Lessons = learned! So, what now? I'd like to get this committed to trunk. Lesson #2 from SoC is that branches suck. I basically just decked out win-deps/ with DLLs from the Mono Windows package (should be SVN externals, perhaps?) and made a few source code changes to get things working with csc (the coalesce operator apparently has a lower priority than the assignment operator - wtf?). The big problem is parallel solutions: having MonoDevelop and Visual Studio solution files sucks powerful bad. MD is moving toward a completely .sln/.csproj/msbuild/xbuild based system, so how soon can we make that file format transition? Also, how is Banshee handling icons (stock and otherwise)? I could look and figure it out, or someone could just tell me. OK, get back to me about those things, and I'll get back to you about quickly I got GStreamer working. [1] http://www.codeplex.com/aspnet/license [2] http://themonkeysgrinder.blogspot.com/2007/06/eets-alive.html _______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
|
|
Re: Windows! (Yes, I said WINDOWS!)Oh, there are a few other particulars that I wanted to mention:
Mono.Cairo. One of the *-sharp.dll wrapper assemblies references Mono.Cairo.dll 1.0.5 but we reference Mono.Cairo.dll 2.0. This kills Aaron's dream of just shoving all of the dependencies in the executing directory: one of the two will need to be registered through the GAC. The other thing is, I had to use the Windows filenames for extern method DLLs. Since Mono has a faculty for DLL mapping, I recommend we use the Windows names in the source and rely on Mono to resolve those to the Unix names when appropriate. The other option is: [DllImport("libglib-2.0-0.dll")] private static extern IntPtr g_filename_to_uri_win32 (IntPtr filename, IntPtr hostname, IntPtr error); [DllImport("libglib-2.0.so")] private static extern IntPtr g_filename_to_uri (IntPtr filename, IntPtr hostname, IntPtr error); if(Environment.OSVersion.Platform == PlatformID.Unix) g_filename_to_uri(filename, hostname, error); else g_filename_to_uri_win32(filename, hostname, error); Which sucks hard. OK, that's really all for now. _______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
|
|
Re: Windows! (Yes, I said WINDOWS!)MonoDevelop supports .sln fine. You could just completely replace all the mds/mdp's with .csproj/.sln files and be done with it. MonoDevelop may even support auto-conversion of mdp -> sln and vice versa, so that may be worth checking out.
Also, no need to reinvent the wheel with the dllimports, just use the windows names and the dll map mechanism in Mono - that's what it's there for :) Alan. On Sun, Aug 31, 2008 at 8:56 PM, Scott Peterson <lunchtimemama@...> wrote: Oh, there are a few other particulars that I wanted to mention: _______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
|
|
Re: Windows! (Yes, I said WINDOWS!)> On Sun, Aug 31, 2008 at 8:56 PM, Scott Peterson <lunchtimemama@...>
> wrote: >> The other thing is, I had to use the Windows filenames for extern >> method DLLs. Since Mono has a faculty for DLL mapping, I recommend we >> use the Windows names in the source and rely on Mono to resolve those >> to the Unix names when appropriate. I've been doing exactly this on OS X. Great work by the way. Eoin _______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
|
|
Re: Windows! (Yes, I said WINDOWS!)I converted Banshee's project layout to sln/csproj targeting Visual Studio 2005 as of yesterday.
--Aaron >>> On 8/31/2008 at 11:50 AM, in message <117799f00808310850i99305b4sbe9a60fc16b9fd0e@...>, "Alan McGovern" <alan.mcgovern@...> wrote: > MonoDevelop supports .sln fine. You could just completely replace all the > mds/mdp's with .csproj/.sln files and be done with it. MonoDevelop may even > support auto-conversion of mdp -> sln and vice versa, so that may be worth > checking out. > > Also, no need to reinvent the wheel with the dllimports, just use the > windows names and the dll map mechanism in Mono - that's what it's there for > :) > > Alan. > > On Sun, Aug 31, 2008 at 8:56 PM, Scott Peterson > <lunchtimemama@...>wrote: > >> Oh, there are a few other particulars that I wanted to mention: >> >> Mono.Cairo. One of the *-sharp.dll wrapper assemblies references >> Mono.Cairo.dll 1.0.5 but we reference Mono.Cairo.dll 2.0. This kills >> Aaron's dream of just shoving all of the dependencies in the executing >> directory: one of the two will need to be registered through the GAC. >> >> The other thing is, I had to use the Windows filenames for extern >> method DLLs. Since Mono has a faculty for DLL mapping, I recommend we >> use the Windows names in the source and rely on Mono to resolve those >> to the Unix names when appropriate. The other option is: >> >> [DllImport("libglib-2.0-0.dll")] >> private static extern IntPtr g_filename_to_uri_win32 (IntPtr filename, >> IntPtr hostname, IntPtr error); >> >> [DllImport("libglib-2.0.so")] >> private static extern IntPtr g_filename_to_uri (IntPtr filename, >> IntPtr hostname, IntPtr error); >> >> if(Environment.OSVersion.Platform == PlatformID.Unix) >> g_filename_to_uri(filename, hostname, error); >> else >> g_filename_to_uri_win32(filename, hostname, error); >> >> Which sucks hard. >> >> OK, that's really all for now. >> _______________________________________________ >> Banshee-list mailing list >> Banshee-list@... >> http://mail.gnome.org/mailman/listinfo/banshee-list >> _______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
|
|
Re: Windows! (Yes, I said WINDOWS!)Sorry to raise a dead thread, but I was wondering if any of this code is checked into trunk/head?
On Thu, Sep 4, 2008 at 1:42 PM, Aaron Bockover <abockover@...> wrote: I converted Banshee's project layout to sln/csproj targeting Visual Studio 2005 as of yesterday. -- http://www.volatileminds.net _______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
|
|
Re: Windows! (Yes, I said WINDOWS!)I have to ask the same question. I would love to get Banshee working on Windows, but as far as I can tell, the changes are not present. I might be wrong, but currently it does not build on windows. Before I start making changes to make it work, I want to ensure that I'm not duplicating work. Scott, are your changes in trunk or in a branch somewhere? If not, would it be possible to either commit them to trunk, create a branch or at the least, post a patch here?
Thank you, Justin Cherniak 2008/9/8 Brandon Perry <bperry.volatile@...>
_______________________________________________ Banshee-list mailing list Banshee-list@... http://mail.gnome.org/mailman/listinfo/banshee-list |
| Free Forum Powered by Nabble | Forum Help |