Hi.
First of all, sorry for jumping at you like that. It seems we simply
have a communication problem.
On Thursday, 11 September 2008 at 15:35, Petit Eric wrote:
> 2008/9/11 Dominik 'Rathann' Mierzejewski <[EMAIL PROTECTED]>:
> > Hi,
> >
> > On Thursday, 11 September 2008 at 09:03, Petit Eric wrote:
> >> Hi Dominik
> >> The tarball you get on OBS (i don't know how) is for build RPM and is
> >> out of date, you can use it for testing pupose with the other
> >> obexftp0.23 and obexftp-csharp RPM located at OBS repository.
> >> For example if you are Fedora9/i386/586 :
> >> http://download.opensuse.org/repositories/home:/surfzoid/Fedora_9/i386/obexftp-0.23-177.1.i386.rpm
> >> and
> >> http://download.opensuse.org/repositories/home:/surfzoid/Fedora_9/i386/csharp-obexftp-0.23-28.1.i386.rpm
> >
> > obexftp is already in Fedora (I maintain it).
> >
> > Where did you get the obexftp-0.23-alpha.tar.bz2 tarball from
> > http://download.opensuse.org/repositories/home:/surfzoid/Fedora_9/src/obexftp-0.23-28.1.src.rpm?
> > It doesn't match the one present at http://triq.net/obexftp/
> The dif is wath christian explain, from OBS repo is the version who
> use the SWIG C# binding, the last one has been changed to don't use
> anymore SWIG but a single class write by christian.
OK. Could someone put it @triq.net/obexftp/ then?
> > Even though it does have C# bindings, it still doesn't let me build
> > cs_obexftp.
> There is compilation error ?
No, but the only new file I get is libcsobexftp.so*. I don't get any
Mono assemblies.
> >> To have the last tarball of source , you will have better luke here :
> >> http://cs-obexftp.svn.sourceforge.net/viewvc/cs-obexftp/trunk/Cs-ObexFtp.tar.gz
> >
> > This tarball still contains binaries. Could you provide one that contains
> > ONLY sources? This tarball doesn't build if I remove the included binaries:
> I explain i don't separe windows stuff from Linux one and will not
> double project, effort and so on.
> The way i folow is to use in the spec file rm -f all unwanted binary .
OK, fine. I deleted the dlls just like you said, but then the message below
appears.
> > [...]
> > make[1]: *** No rule to make target `libbfb.dll', needed by
> > `bin/Release//libbfb.dll'. Stop.
> > make[1]: Leaving directory
> > `/home/local/rathann/build/SOURCES/cs_obexftp/Cs-ObexFtp/AllDll'
> > make: *** [all-recursive] Error 1
> >
> >> or if you want to update frequently use svn cli :
> >> svn co
> >> https://cs-obexftp.svn.sourceforge.net/svnroot/cs-obexftp/trunk/Cs-ObexFtp/
> >
> > My point is still valid even if I use your svn. You actually have the same
> > binaries in svn. That is not acceptable.
> >
> >> But as say christian a new method/single class is used now, so monitor
> >> release in the obexftp repository :
> >> http://triq.net/obexftp/ to take the last 0.23 and also new of christian.
> >
> > That's what I tried, but there's nothing newer than 0.23-alpha.
> Sorry for my poor english : " Monitoring it to wait news of christian
> about his release".
Yes, I understood that. I thought there was some new release just now.
> >> At this time, because too mutch problem and the C# binding in obexftp
> >> doesn't work , Cs-Obexftp project is in stand-by, normaly durring
> >> october studiant should suscribe to the project and participate to it.
> >
> >> About Magic recipe lol :D, no you can contact me at ICQ if you want :
> >> 485026427
> >
> > I don't use ICQ. Why is this so secret that you cannot answer my question
> > on this mailing list, publicly?
> Absoluty no, i beleve there isn't magic recipe, i just give you ICQ
> number to be more helpfull and help step by step in real time; again
> sorry for my poor english, it seam i don't understand correctly your
> question or my response are bad, again sorry..
Could you come to IRC then? For example to the #openobex channel on
the Freenode network (chat.eu.freenode.net server, see
http://www.freenode.net/).
> >> The win32 dll is in my source for a very simple reason, i made pkg for
> >> Linux and Win32 too :-) and don't take the time to separate all need
> >> file, that have no incident for the rest.
> >>
> >> It is complety right , we need to get all in the same version and a good
> >> howto
> >
> > So let me get this straight: you distribute binaries without the
> > accompanying
> > sources?
> NO, ALL sources are aviable, but , some dll are the dll of obexftp
But compiling obexftp, even with csharp bindings doesn't produce any Mono
assemblies.
How can I compile them myself?
> and openobex win32 portage other are Assembly .NET/MONO where source are
> in Cs-Obexftp solution.
The sources from Cs_Obexftp compile just fine.
> > Well, since you claim to distribute them under the GPLv2+, I ask you
> > to provide the sources and the instructions to build those binaries from
> > them.
> > Otherwise you're not complying with your own license terms.
> finaly, to compile third dll :
> http://dev.zuckschwerdt.org/openobex/wiki/ObexWin32
But that's for Windows, isn't it? Again, how can I build Mono assemblies
on Linux?
> to find the compiled binary http://triq.net/obexftp/obex-win32.zip
As I said, precompiled binaries are not acceptable for building
a package for Fedora.
> For Cs-Obexftp, i need to include them in my solution and say to copy
> them in output dir, but i will think to an solution ...
> At this time the only way is to compil it with this binary include or
> to modify the cs_obexftp.csprj to exclude them, perhap's a patch could
> be good.
> After silmply clean the output of unwanted binary, the one needed to
> have cs_obexftp running under linux are :
> - BluetoothWrapper.dll
> - Cs-ObexFtp.exe
> - the 2 Cs-Obexftp.ressource.dll
> - obexftp.dll
OK, that was a good clue, why didn't you say that earlier?
Using the attached patch, I was able to build this successfully.
Thanks.
> But once again, the good combinaison is the file provide in my OBS
> repository,
And again I have to say: I can't just use the binaries you provide,
even if I wanted to.
> if you take the tarball from my svn you will need to use
> the last 0.23 alpha from openobex site.
You are unclear here. What do you mean by "use the last 0.23 alpha from
openobex site"? Use how? As I said, building obexftp-0.23-alpha.tar.bz2
doesn't produce any Mono assemblies.
Regards,
R.
--
Fedora http://fedoraproject.org/wiki/User:Rathann
Livna http://rpm.livna.org | MPlayer http://mplayerhq.hu
"Faith manages."
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
diff -up cs_obexftp-1.0.0.18/Makefile.mono cs_obexftp-1.0.0.18/Makefile
--- cs_obexftp-1.0.0.18/Makefile.mono 2008-08-02 15:00:23.000000000 +0200
+++ cs_obexftp-1.0.0.18/Makefile 2008-09-11 19:44:39.000000000 +0200
@@ -12,10 +12,10 @@ include $(top_srcdir)/rules.make
#Warning: This is an automatically generated file, do not edit!
ifeq ($(CONFIG),DEBUG)
- SUBDIRS = BluetoothWin/BluetoothWrapper MonoUpdater AllDll
BluetoothWin/Bluetooth Cs-ObexFtp
+ SUBDIRS = BluetoothWin/BluetoothWrapper BluetoothWin/Bluetooth Cs-ObexFtp
endif
ifeq ($(CONFIG),RELEASE)
- SUBDIRS = BluetoothWin/BluetoothWrapper MonoUpdater AllDll
BluetoothWin/Bluetooth Cs-ObexFtp
+ SUBDIRS = BluetoothWin/BluetoothWrapper BluetoothWin/Bluetooth Cs-ObexFtp
endif
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users
