KDE/kdebindings

SVN commit 671745 by arnorehn:

* Improved the build system:
	* Added FindMono.cmake to find mono, gmcs, mcs and gacutil
	* Added CSharpMacros.cmake which consists of macros for
dealing with C#.
	  It's now much easier to build C# libraries and
executables and to
	  install them.
	  Further, a C# target is only built if the output file is
missing
	  or the sources were modified.
* Updated all CMakeLists.txt to work with the improved build
system.

CCMAIL: kde-bindingskde.org



 A             cmake/modules/CSharpMacros.cmake  
 A             cmake/modules/FindMono.cmake  
 M  +7 -18     csharp/CMakeLists.txt  
 M  +11 -8     csharp/qyoto/CMakeLists.txt  
 M  +11 -0     csharp/qyoto/ChangeLog  
 M  +0 -2      csharp/qyoto/examples/CMakeLists.txt  
 M  +3 -4     
csharp/qyoto/examples/graphicsview/collidingmice/CMakeLists.
txt  
 M  +3 -4     
csharp/qyoto/examples/itemviews/simpletreemodel/CMakeLists.t
xt  
 M  +4 -5     
csharp/qyoto/examples/qdbus/chat/CMakeLists.txt  
 M  +4 -3     
csharp/qyoto/examples/qdbus/complexpingpong/CMakeLists.txt 

 M  +2 -2     
csharp/qyoto/examples/qdbus/listnames/CMakeLists.txt  
 M  +4 -3     
csharp/qyoto/examples/qdbus/pingpong/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/qdbus/remotecontrolledcar/car/CMakeLis
ts.txt  
 M  +3 -4     
csharp/qyoto/examples/qdbus/remotecontrolledcar/controller/C
MakeLists.txt  
 M  +0 -1      csharp/qyoto/examples/tutorial/CMakeLists.txt
 
 M  +2 -1     
csharp/qyoto/examples/tutorial/t1/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t10/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t11/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t12/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t13/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t14/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t2/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t3/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t4/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t5/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t6/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t7/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t8/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/tutorial/t9/CMakeLists.txt  
 M  +2 -2     
csharp/qyoto/examples/widgets/analogclock/CMakeLists.txt  


_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

On Tuesday 05 June 2007, Arno Rehn wrote:
> SVN commit 671745 by arnorehn:
>
> * Improved the build system:
> 	* Added FindMono.cmake to find mono, gmcs, mcs and
gacutil
> 	* Added CSharpMacros.cmake which consists of macros
for dealing with C#.
> 	  It's now much easier to build C# libraries and
executables and to
> 	  install them.
> 	  Further, a C# target is only built if the output
file is missing
> 	  or the sources were modified.
> * Updated all CMakeLists.txt to work with the improved
build system.
That looks really good - I wonder if we're the first people
to use cmake 
seriously with C#/Mono. Maybe we can suggest that a FindMono
module is 
included with the cmake release?

I'm keen to get a release out, as I think we've got a lot of
really good stuff 
now. Here is a release TODO list:

- Update the AUTHORS file
- Add a README summarising how Qyoto implements
slots/signals/properties and 
how it differs from the C++ api. Describe how the uics and
csrcc tools work.
- Write a release notice, and send to kde-announce, and
anywhere else 
appropriate
- Write an article for KDE Dot News, combining the above
texts
- Build a release package and put it on the qyoto.org site
- Update the TODO and remove things we've done, and add
items which haven't 
been implemented for the first release.

Anything else?

-- Richard
_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

Quoting Richard Dale <rdalefoton.es>:
> Maybe we can suggest that a FindMono module is
> included with the cmake release?

Good luck with that. There are lots of FindXXXX.cmake
modules in the  
CMake bugtracker waiting to be included in CMake.

Further, there are hundreds of FindWhatever.cmake modules
out there  
but people no longer bother with sending them to the CMake
mailing  
list or the bugtracker because they get no answer from
Kitware.

As Alexander Neundorf works for Kitware, maybe
FindMono.cmake will  
make its way into CMake but I would not cound on that.

(Yeah, I am a bit frustrated with this)

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to the amount of work, I usually need 10 days to
answer)

_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

Am Dienstag, 5. Juni 2007 schrieb Richard Dale:
> On Tuesday 05 June 2007, Arno Rehn wrote:
> > SVN commit 671745 by arnorehn:
> >
> > * Improved the build system:
> > 	* Added FindMono.cmake to find mono, gmcs, mcs
and gacutil
> > 	* Added CSharpMacros.cmake which consists of
macros for dealing with C#.
> > 	  It's now much easier to build C# libraries and
executables and to
> > 	  install them.
> > 	  Further, a C# target is only built if the
output file is missing
> > 	  or the sources were modified.
> > * Updated all CMakeLists.txt to work with the
improved build system.
>
> That looks really good - I wonder if we're the first
people to use cmake
> seriously with C#/Mono. Maybe we can suggest that a
FindMono module is
> included with the cmake release?
>
> I'm keen to get a release out, as I think we've got a
lot of really good
> stuff now. Here is a release TODO list:
>
> - Update the AUTHORS file
> - Add a README summarising how Qyoto implements
slots/signals/properties
> and how it differs from the C++ api. Describe how the
uics and csrcc tools
> work. - Write a release notice, and send to
kde-announce, and anywhere else
> appropriate
> - Write an article for KDE Dot News, combining the
above texts
> - Build a release package and put it on the qyoto.org
site
> - Update the TODO and remove things we've done, and add
items which haven't
> been implemented for the first release.
>
> Anything else?
I think that should be it.


-- 
Arno Rehn
arnoarnorehn.de
_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

On Tuesday 05 June 2007, Pau Garcia i Quiles wrote:
> Quoting Richard Dale <rdalefoton.es>:
> > Maybe we can suggest that a FindMono module is
> > included with the cmake release?
>
> Good luck with that. There are lots of FindXXXX.cmake
modules in the
> CMake bugtracker waiting to be included in CMake.
>
> Further, there are hundreds of FindWhatever.cmake
modules out there
> but people no longer bother with sending them to the
CMake mailing
> list or the bugtracker because they get no answer from
Kitware.
>
> As Alexander Neundorf works for Kitware, maybe
FindMono.cmake will
> make its way into CMake but I would not cound on that.
>
> (Yeah, I am a bit frustrated with this)
Oh, that sounds a shame. I think that was one of the many
things wrong with 
autoconf/automake - it didn't have basic features as
standard like looking 
for java even, and didn't seem to interact much with the
Free Software 
community. The kde version of libtool didn't work with gcj
for *really* 
obvious reasons, and I never even knew who to report it to
or whether anyone 
was interested. And obscure things like working with
Objective-C/GnuStep 
actually got worse over the years.

-- Richard

_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

Am Dienstag, 5. Juni 2007 schrieb Pau Garcia i Quiles:
> Quoting Richard Dale <rdalefoton.es>:
> > Maybe we can suggest that a FindMono module is
> > included with the cmake release?
>
> Good luck with that. There are lots of FindXXXX.cmake
modules in the
> CMake bugtracker waiting to be included in CMake.
>
> Further, there are hundreds of FindWhatever.cmake
modules out there
> but people no longer bother with sending them to the
CMake mailing
> list or the bugtracker because they get no answer from
Kitware.
>
> As Alexander Neundorf works for Kitware, maybe
FindMono.cmake will
> make its way into CMake but I would not cound on that.
>
> (Yeah, I am a bit frustrated with this)
Well, I can understand kitware somehow. I think they get a
few modules each 
week... If they'd check each one and include it in their
releases, it'd be 
probably too much work.
I think it's better if the modules are availible on the
homepage of the 
project, so for example could mono provide a FindMono.cmake
on 
www.mono-project.com for every developer to dowload. If it's
needed, we can 
include it in out releases.

-- 
Arno Rehn
arnoarnorehn.de
_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

sorry to hijack the thread here, but as anyone tested Qyoto
on OS X against the
4.3.0 .dmg download provided by Trolltech?  I'm getting
OS/KERN errors when linking
against the QtScript framework during the make process, but
I'm not sure if it's
Qyoto related or a bug in the precompiled QtScript
framework.  If I remove QtScript
from the FindQt4.cmake stuff and retry, it build
successfully.

_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

On 6/5/07, Richard Dale <rdalefoton.es> wrote:
> On Tuesday 05 June 2007, Arno Rehn wrote:
> > SVN commit 671745 by arnorehn:
> >
> > * Improved the build system:
> >       * Added FindMono.cmake to find mono, gmcs,
mcs and gacutil
> >       * Added CSharpMacros.cmake which consists of
macros for dealing with C#.
> >         It's now much easier to build C# libraries
and executables and to
> >         install them.
> >         Further, a C# target is only built if the
output file is missing
> >         or the sources were modified.
> > * Updated all CMakeLists.txt to work with the
improved build system.
> That looks really good - I wonder if we're the first
people to use cmake
> seriously with C#/Mono. Maybe we can suggest that a
FindMono module is
> included with the cmake release?
>
> I'm keen to get a release out, as I think we've got a
lot of really good stuff
> now. Here is a release TODO list:
>
> - Update the AUTHORS file
> - Add a README summarising how Qyoto implements
slots/signals/properties and
> how it differs from the C++ api. Describe how the uics
and csrcc tools work.
> - Write a release notice, and send to kde-announce, and
anywhere else
> appropriate
> - Write an article for KDE Dot News, combining the
above texts
> - Build a release package and put it on the qyoto.org
site
> - Update the TODO and remove things we've done, and add
items which haven't
> been implemented for the first release.
>
> Anything else?
>

I think it would be good to contact the mono developers to
post either
an Article in Mono, post news in their site and/or add a
Qyoto section
to http://www.m
ono-project.com/Gui_Toolkits

David
_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

On Tuesday 05 June 2007, Caleb Tennis wrote:
> sorry to hijack the thread here, but as anyone tested
Qyoto on OS X against
> the 4.3.0 .dmg download provided by Trolltech?  I'm
getting OS/KERN errors
> when linking against the QtScript framework during the
make process, but
> I'm not sure if it's Qyoto related or a bug in the
precompiled QtScript
> framework.  If I remove QtScript from the FindQt4.cmake
stuff and retry, it
> build successfully.
I haven't tried it with the latest Qt lib on Mac OS X, but I
wasn't intending 
to include the QtScript classes in the smoke library, or
link Smoke against 
it. Maybe we need to do something like set the name of the
QtScript lib to 
spaces. I think we need to do something similar for QtDBus
when that isn't 
found, otherwise you get an error.

-- Richard
_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings

Am Dienstag, 5. Juni 2007 schrieb Richard Dale:
> On Tuesday 05 June 2007, Caleb Tennis wrote:
> > sorry to hijack the thread here, but as anyone
tested Qyoto on OS X
> > against the 4.3.0 .dmg download provided by
Trolltech?  I'm getting
> > OS/KERN errors when linking against the QtScript
framework during the
> > make process, but I'm not sure if it's Qyoto
related or a bug in the
> > precompiled QtScript framework.  If I remove
QtScript from the
> > FindQt4.cmake stuff and retry, it build
successfully.
>
> I haven't tried it with the latest Qt lib on Mac OS X,
but I wasn't
> intending to include the QtScript classes in the smoke
library, or link
> Smoke against it.
Uhm, why? I think it would be nice to be able to control for
example a C# app 
with ECMAScript.
Could be somehow useful, sometimes, couldn't it?

-- 
Arno Rehn
arnoarnorehn.de
_______________________________________________
Kde-bindings mailing list
Kde-bindingskde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-bindings