Re: Status of cmake into kde
At 05:09 PM 3/10/2006, Peter Kümmel wrote: >Alex Caudill wrote: >> Could anyone comment on the steps taken to build kdelibs with msvc? > >A first version is now online at: > >http://www.kdelibs.com/ > >But to change something you need a account which >you can get from Jaroslaw Staniek: >js !"§$-- AT --!"§$ iideapl I would change one thing. When you build kdewin32.lib, you should create a separate build directory for it. Then you can remove the step in building kdelibs that says del CMakeCache.txt. Basically, use a separate build tree for kdewin32 and kdelibs. -Bill ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
Alex Caudill wrote: > Could anyone comment on the steps taken to build kdelibs with msvc? A first version is now online at: http://www.kdelibs.com/ But to change something you need a account which you can get from Jaroslaw Staniek: js !"§$-- AT --!"§$ iideapl Cheers, Peter ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: check_include_files
>> It seems that CHECK_INCLUDE_FILES is invoked in a couple CMakeList.txt >> files without declaring INCLUDE(CheckIncludeFiles) first; has anyone else >> ran into this? >> >> Is it only an issue when using cmakesetup.exe? >> Affected files: >> Kdelibs/modules/cmake/FindACL.cmake >> Kdelibs/kjs/CMakeLists.txt >I also have problems with this macro. >Is it a new one which is only in cvs of cmake? After adding INCLUDE(CheckIncludeFiles) to both files, the latest CVS of CMake works fine. Cursory googling suggests it's been there since at least April 2005, so it seems like it was just a simple error. I think it's sorta interesting that it didn't break *nix builds, though. Or did it? ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: check_include_files
Alex Caudill wrote: > It seems that CHECK_INCLUDE_FILES is invoked in a couple CMakeList.txt files > > > without declaring INCLUDE(CheckIncludeFiles) first; has anyone else ran into > this? > > Is it only an issue when using cmakesetup.exe? > > > > Affected files: > > Kdelibs/modules/cmake/FindACL.cmake > > Kdelibs/kjs/CMakeLists.txt > I also have problems with this macro. Is it a new one which is only in cvs of cmake? ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
William A. Hoffman schrieb: > At 01:31 PM 3/10/2006, Alex Caudill wrote: > > >> -Original Message- >> From: Peter Kümmel [mailto:[EMAIL PROTECTED] >> Sent: Friday, March 10, 2006 12:14 PM >> To: kde-buildsystem@kde.org >> Subject: Re: Status of cmake into kde >> >> Alex Caudill wrote: Could anyone comment on the steps taken to build kdelibs with msvc? >>> Here on the list, for "personal use" only? :) >>> Were are the places of documentation, svn and a wiki? >>> Peter >> I'm not a very good programmer, but I have a few fairly snappy machines here >> and I'd like to help out and learn a bit. I'm a half-decent writer, so maybe >> I could make some contributions to the wiki? Where is it located? I've >> documented the steps I've taken so far... sorry if the formatting is >> horrible. This may be wildly different than the process you guys use, the >> most successful build I've had so far had over 100 errors, and more than >> 1000 warnings. > > So, when you get things going, it would be nice if you were to set up a > dashboard for the windows build. Would you be able to run nightly jobs > on your machine? If so, I can help you set them up. The results would go > here: > http://public.kitware.com/dashboard.php?name=kde > > I have not yet set up a windows build, as it is not all compiling yet. > However, it might be time to disable parts of the build that do not work, > and enable the parts that do work, so that ground is not lost. (i.e. what > is working now, stays working.) As new stuff starts to work, it can be added > to the build. I really would like to do this but as you know I've some troubles with running cmake on my computer ;) Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
check_include_files
It seems that CHECK_INCLUDE_FILES is invoked in a couple CMakeList.txt files without declaring INCLUDE(CheckIncludeFiles) first; has anyone else ran into this? Is it only an issue when using cmakesetup.exe? Affected files: Kdelibs/modules/cmake/FindACL.cmake Kdelibs/kjs/CMakeLists.txt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Status of cmake into kde
At 01:31 PM 3/10/2006, Alex Caudill wrote: >-Original Message- >From: Peter Kümmel [mailto:[EMAIL PROTECTED] >Sent: Friday, March 10, 2006 12:14 PM >To: kde-buildsystem@kde.org >Subject: Re: Status of cmake into kde > >Alex Caudill wrote: >>> Could anyone comment on the steps taken to build kdelibs with msvc? >>> > >> Here on the list, for "personal use" only? :) >> Were are the places of documentation, svn and a wiki? >> Peter > >I'm not a very good programmer, but I have a few fairly snappy machines here >and I'd like to help out and learn a bit. I'm a half-decent writer, so maybe >I could make some contributions to the wiki? Where is it located? I've >documented the steps I've taken so far... sorry if the formatting is >horrible. This may be wildly different than the process you guys use, the >most successful build I've had so far had over 100 errors, and more than >1000 warnings. So, when you get things going, it would be nice if you were to set up a dashboard for the windows build. Would you be able to run nightly jobs on your machine? If so, I can help you set them up. The results would go here: http://public.kitware.com/dashboard.php?name=kde I have not yet set up a windows build, as it is not all compiling yet. However, it might be time to disable parts of the build that do not work, and enable the parts that do work, so that ground is not lost. (i.e. what is working now, stays working.) As new stuff starts to work, it can be added to the build. Now all we need is someone with a Mac that is free for several hours each night -Bill ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
Alex Caudill wrote: > I'm not a very good programmer, but I have a few fairly snappy machines here > and I'd like to help out and learn a bit. I'm a half-decent writer, so maybe > I could make some contributions to the wiki? That's great! We really need compiling instructions! >Where is it located? I've > documented the steps I've taken so far... sorry if the formatting is > horrible. This may be wildly different than the process you guys use, the > most successful build I've had so far had over 100 errors, and more than > 1000 warnings. > ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
On Friday 10 March 2006 12:04, Christian Ehrlicher wrote: > Brad King schrieb: > > Peter Kuemmel wrote: > >> */Brad King <[EMAIL PROTECTED]>/* wrote: > >> I've found that a KDE_DEPRECATED-style macro is insufficient across > >> compilers. Some compilers want the decoration before the method and > >> some want it after the method. In VTK I created a "VTK_LEGACY" macro > >> that surrounds the method declaration. > >> > >> If we really need both positions then we could support this by > >> using two macros: > >> > >> KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POST > >> > >> or > >> > >> KDE_DEPRECATED_PRE > >> void foo() > >> KDE_DEPRECATED_POST > >> > >> So we could find a macro solution for all compiler. > > > > ...as against just > > > > KDE_DEPRECATED(void foo()); > > > > with my suggestion. > > This could be an idea but in the last discussion I heard something like > 'we support the same compiler like Qt and therefor we also could use the > same deprecated-macro' ... > > In which places is KDE_DEPRECATED used? Only kdelibs? I won't break the > complete kde4 source when I change kde_deprecated in any way... :) > KDE_DEPRECATED is used in other modules (kdenetwork/kopete comes to mind) so a complete sweep of trunk/KDE will be needed, unless you just do kdelibs and leave it to the app maintainers to fix their own apps. -- Matt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
Alex Caudill schrieb: > > -Original Message- > From: Peter Kümmel [mailto:[EMAIL PROTECTED] > Sent: Friday, March 10, 2006 12:14 PM > To: kde-buildsystem@kde.org > Subject: Re: Status of cmake into kde > > Alex Caudill wrote: >>> Could anyone comment on the steps taken to build kdelibs with msvc? >>> > >> Here on the list, for "personal use" only? :) >> Were are the places of documentation, svn and a wiki? >> Peter > > I'm not a very good programmer, but I have a few fairly snappy machines here > and I'd like to help out and learn a bit. I'm a half-decent writer, so maybe > I could make some contributions to the wiki? Where is it located? I've > documented the steps I've taken so far... sorry if the formatting is > horrible. This may be wildly different than the process you guys use, the > most successful build I've had so far had over 100 errors, and more than > 1000 warnings. > > Is this the right list, or should I post to kde-windows? > > Prerequisites: Visual Studio 2005 > GNUWin32: > bzip2, zlib, libxml, libxslt, openssl, pcre, giflib, > jpeg Some are missing (agg2, libpng, don't know what else ;) ) > An implementation of perl: Cygwin, MinGW, or ActivePerl. > I'm (trying to) use ActivePerl. > > > Step 1.) Download qt-win-opensource-4.1.1.zip and Qt/4.1.x MSVC patch > > Step 2.) Apply patch to Qt; qconfigure msvc2005 > > Step 3.) Set the QTDIR environmental variable. Add %QTDIR%/bin to your PATH. > > Step 4.) Acquire a stable build of CMake (for bootstrapping) and latest > CMake CVS. > > Step 5.) Build cmake CVS (run stable cmakesetup, load the resultant project > file in VS, consult documentation) > > Step 6.) Acquire latest SVN of KDELibs (I suggest using tortoisesvn) Step 6.5 build & install kdelibs/win with cmake/cmakesetup > > Step 7.) cd kdelibs/cmake ; cmakesetup.exe ; load .proj files, build ? Imho not needed > > Step 8.) in kdelibs root: cmakesetup.exe ; load .proj files, build > > > Am I missing anything? Thanks in advance! > Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Status of cmake into kde
>> Step 7.) cd kdelibs/cmake ; cmakesetup.exe ; load .proj files, build >? Imho not needed I meant kdelibs/win - this is why I'm not a very good programmer =) ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Matt Rogers schrieb: > On Friday 10 March 2006 12:04, Christian Ehrlicher wrote: >> Brad King schrieb: >>> Peter Kuemmel wrote: */Brad King <[EMAIL PROTECTED]>/* wrote: I've found that a KDE_DEPRECATED-style macro is insufficient across compilers. Some compilers want the decoration before the method and some want it after the method. In VTK I created a "VTK_LEGACY" macro that surrounds the method declaration. If we really need both positions then we could support this by using two macros: KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POST or KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POST So we could find a macro solution for all compiler. >>> ...as against just >>> >>> KDE_DEPRECATED(void foo()); >>> >>> with my suggestion. >> This could be an idea but in the last discussion I heard something like >> 'we support the same compiler like Qt and therefor we also could use the >> same deprecated-macro' ... >> >> In which places is KDE_DEPRECATED used? Only kdelibs? I won't break the >> complete kde4 source when I change kde_deprecated in any way... :) >> > > KDE_DEPRECATED is used in other modules (kdenetwork/kopete comes to mind) so > a > complete sweep of trunk/KDE will be needed, unless you just do kdelibs and > leave it to the app maintainers to fix their own apps. Then the idea to use KDE_DEPRECATED() is not easy to realise. The only way to to this would be to use a new macro name... Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Status of cmake into kde
-Original Message- From: Peter Kümmel [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 12:14 PM To: kde-buildsystem@kde.org Subject: Re: Status of cmake into kde Alex Caudill wrote: >> Could anyone comment on the steps taken to build kdelibs with msvc? >> > Here on the list, for "personal use" only? :) > Were are the places of documentation, svn and a wiki? > Peter I'm not a very good programmer, but I have a few fairly snappy machines here and I'd like to help out and learn a bit. I'm a half-decent writer, so maybe I could make some contributions to the wiki? Where is it located? I've documented the steps I've taken so far... sorry if the formatting is horrible. This may be wildly different than the process you guys use, the most successful build I've had so far had over 100 errors, and more than 1000 warnings. Is this the right list, or should I post to kde-windows? Prerequisites: Visual Studio 2005 GNUWin32: bzip2, zlib, libxml, libxslt, openssl, pcre, giflib, jpeg An implementation of perl: Cygwin, MinGW, or ActivePerl. I'm (trying to) use ActivePerl. Step 1.) Download qt-win-opensource-4.1.1.zip and Qt/4.1.x MSVC patch Step 2.) Apply patch to Qt; qconfigure msvc2005 Step 3.) Set the QTDIR environmental variable. Add %QTDIR%/bin to your PATH. Step 4.) Acquire a stable build of CMake (for bootstrapping) and latest CMake CVS. Step 5.) Build cmake CVS (run stable cmakesetup, load the resultant project file in VS, consult documentation) Step 6.) Acquire latest SVN of KDELibs (I suggest using tortoisesvn) Step 7.) cd kdelibs/cmake ; cmakesetup.exe ; load .proj files, build Step 8.) in kdelibs root: cmakesetup.exe ; load .proj files, build Am I missing anything? Thanks in advance! ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
Alex Caudill wrote: > Could anyone comment on the steps taken to build kdelibs with msvc? > Here on the list, for "personal use" only? :) Were are the places of documentation, svn and a wiki? Peter ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Brad King schrieb: > Peter Kuemmel wrote: >> */Brad King <[EMAIL PROTECTED]>/* wrote: >> I've found that a KDE_DEPRECATED-style macro is insufficient across >> compilers. Some compilers want the decoration before the method and >> some want it after the method. In VTK I created a "VTK_LEGACY" macro >> that surrounds the method declaration. >> >> If we really need both positions then we could support this by >> using two macros: >> >> KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POST >> >> or >> >> KDE_DEPRECATED_PRE >> void foo() >> KDE_DEPRECATED_POST >> >> So we could find a macro solution for all compiler. > > ...as against just > > KDE_DEPRECATED(void foo()); > > with my suggestion. This could be an idea but in the last discussion I heard something like 'we support the same compiler like Qt and therefor we also could use the same deprecated-macro' ... In which places is KDE_DEPRECATED used? Only kdelibs? I won't break the complete kde4 source when I change kde_deprecated in any way... :) Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Brad King wrote: > Peter Kuemmel wrote: >> */Brad King <[EMAIL PROTECTED]>/* wrote: >> I've found that a KDE_DEPRECATED-style macro is insufficient across >> compilers. Some compilers want the decoration before the method and >> some want it after the method. In VTK I created a "VTK_LEGACY" macro >> that surrounds the method declaration. >> >> If we really need both positions then we could support this by >> using two macros: >> >> KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POST >> >> or >> >> KDE_DEPRECATED_PRE >> void foo() >> KDE_DEPRECATED_POST >> >> So we could find a macro solution for all compiler. > > ...as against just > > KDE_DEPRECATED(void foo()); > > with my suggestion. > > -Brad Oh, I've overseen the argument taking macro. Yes, your approach is better. Peter ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Status of cmake into kde
Could anyone comment on the steps taken to build kdelibs with msvc? ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Peter Kuemmel wrote: > */Brad King <[EMAIL PROTECTED]>/* wrote: > I've found that a KDE_DEPRECATED-style macro is insufficient across > compilers. Some compilers want the decoration before the method and > some want it after the method. In VTK I created a "VTK_LEGACY" macro > that surrounds the method declaration. > > If we really need both positions then we could support this by > using two macros: > > KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POST > > or > > KDE_DEPRECATED_PRE > void foo() > KDE_DEPRECATED_POST > > So we could find a macro solution for all compiler. ...as against just KDE_DEPRECATED(void foo()); with my suggestion. -Brad ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Brad King <[EMAIL PROTECTED]> wrote:I've found that a KDE_DEPRECATED-style macro is insufficient across compilers. Some compilers want the decoration before the method and some want it after the method. In VTK I created a "VTK_LEGACY" macro that surrounds the method declaration.If we really need both positions then we could support this byusing two macros:KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POSTor KDE_DEPRECATED_PRE void foo() KDE_DEPRECATED_POSTSo we could find a macro solution for all compiler.Peter Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze. ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
On Friday 10 March 2006 17:31, you wrote: > Alexander Neundorf schrieb: > > On Friday 10 March 2006 16:09, Laurent Montel wrote: > >> Hi, > >> I put a status of cmake into kde after this week. > >> Now > >> kdelibs/kdebase/kdetoys/kdeedu/kdeaccessibility/kdenetwork/kdepim/kdegam > >>es/ kdeadmin/kdeutils have cmake support. Now all compile completly for > >> all is in progress. There are again some errors and missing module to > >> test lib/header. > >> > >> For the moment I don't have report about compile test under Windows or > >> MacOs so I don't know if it compiles fine. > > kdelibs compiles nearly complete with msvc (currently working on a > simple mmap implementation for kdewin32 to fix makekdewidgets). the rest > is untested on win32 afaik. > > >> I need some help to finish to port it. > > > > I won't be able to help much in the next days, I'll be at the Cebit for > > KDE :-) > > Tomorrow too? Yes, saturday to monday. Looking forward to meet you :-) Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Status of cmake into kde
> -Original Message- > From: Laurent Montel [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 10 de Março de 2006 15:09 > To: kde-buildsystem@kde.org > Subject: Status of cmake into kde > > For the moment I don't have report about compile test under Windows or > MacOs > so I don't know if it compiles fine. With minwg I can compile all but kstyles, kinit, khtml and kjsembed modules. Paulo ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Christian Ehrlicher wrote:
> David Faure schrieb:
>
>>>It is working, but KDE_DEPRECATED is placed behind the functions in most
>>>of the cases and I won't change this in every kdelibs-header...
>>
>>Well someone has to do it, and preferrably someone who can see the
>>problematic instances... :)
>>
>
> Ok, I'll take a look on this when makekdewidgets is working :)
I've found that a KDE_DEPRECATED-style macro is insufficient across
compilers. Some compilers want the decoration before the method and
some want it after the method. In VTK I created a "VTK_LEGACY" macro
that surrounds the method declaration.
The full definition is shown below. There is a "silent" mode to disable
the warnings. It also supports a "remove" mode in which deprecated code
is removed from the build which is useful for making sure applications
do not use any deprecated methods.
The header file declaring the method does this:
VTK_LEGACY(void MyMethod());
and the source file defining the method does this:
#ifndef VTK_LEGACY_REMOVE
void MyClass::MyMethod()
{
}
#endif
If someone is going to make a sweep through KDE's version of this I
suggest a similar design be used...at least for the header file part but
perhaps without the REMOVE support.
-Brad
// Define VTK_LEGACY macro to mark legacy methods where they are
// declared in their class. Example usage:
//
// // @deprecated Replaced by MyOtherMethod() as of VTK 5.0.
// VTK_LEGACY(void MyMethod());
#if defined(VTK_LEGACY_REMOVE)
// Remove legacy methods completely. Put a bogus declaration in
// place to avoid stray semicolons because this is an error for some
// compilers. Using a class forward declaration allows any number
// of repeats in any context without generating unique names.
# define VTK_LEGACY(method) class vtkLegacyMethodRemoved
#elif defined(VTK_LEGACY_SILENT) || defined(VTK_WRAPPING_CXX)
// Provide legacy methods with no warnings.
# define VTK_LEGACY(method) method
#else
// Setup compile-time warnings for uses of deprecated methods if
// possible on this compiler.
# if defined(__GNUC__) && !defined(__INTEL_COMPILER) && (__GNUC__ > 3 ||
(__GNUC__ == 3 && __GNUC_MINOR__ >= 1))
# define VTK_LEGACY(method) method __attribute__((deprecated))
# elif defined(_MSC_VER) && _MSC_VER >= 1300
# define VTK_LEGACY(method) __declspec(deprecated) method
# else
# define VTK_LEGACY(method) method
# endif
#endif
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
David Faure schrieb: >> It is working, but KDE_DEPRECATED is placed behind the functions in most >> of the cases and I won't change this in every kdelibs-header... > > Well someone has to do it, and preferrably someone who can see the > problematic instances... :) > Ok, I'll take a look on this when makekdewidgets is working :) Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
> It is working, but KDE_DEPRECATED is placed behind the functions in most > of the cases and I won't change this in every kdelibs-header... Well someone has to do it, and preferrably someone who can see the problematic instances... :) -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
Peter Kümmel schrieb: > kdemacros: > > #ifndef KDE_DEPRECATED > # ifndef Q_CC_MSVC > # define KDE_DEPRECATED Q_DECL_DEPRECATED > # else > # define KDE_DEPRECATED > # endif > #endif > > Why is KDE_DEPRECATED disabled for msvc? > Does it still not work, even not placed in front > of the functions? It is working, but KDE_DEPRECATED is placed behind the functions in most of the cases and I won't change this in every kdelibs-header... Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: KDE_DEPRECATED
On Friday 10 March 2006 17:44, Peter Kümmel wrote: > > kdemacros: > > #ifndef KDE_DEPRECATED > # ifndef Q_CC_MSVC > # define KDE_DEPRECATED Q_DECL_DEPRECATED > # else > # define KDE_DEPRECATED > # endif > #endif > > Why is KDE_DEPRECATED disabled for msvc? > Does it still not work, even not placed in front > of the functions? Looks like Christian made this change by mistake, I think you should revert it. r516901 | chehrlic | 2006-03-09 06:58:46 +0100 (Thu, 09 Mar 2006) sync kdemacros.h.cmake with kdemacros.h.in (KDE_DEPRECATED) CCMAIL: [EMAIL PROTECTED] Index: kdemacros.h.in === --- kdemacros.h.in (revision 516900) +++ kdemacros.h.in (revision 516901) @@ -147,7 +147,11 @@ */ #ifndef KDE_DEPRECATED +# ifndef Q_CC_MSVC # define KDE_DEPRECATED Q_DECL_DEPRECATED +# else +# define KDE_DEPRECATED +# endif #endif -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
KDE_DEPRECATED
kdemacros: #ifndef KDE_DEPRECATED # ifndef Q_CC_MSVC # define KDE_DEPRECATED Q_DECL_DEPRECATED # else # define KDE_DEPRECATED # endif #endif Why is KDE_DEPRECATED disabled for msvc? Does it still not work, even not placed in front of the functions? Peter ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
Alexander Neundorf schrieb: > On Friday 10 March 2006 16:09, Laurent Montel wrote: >> Hi, >> I put a status of cmake into kde after this week. >> Now >> kdelibs/kdebase/kdetoys/kdeedu/kdeaccessibility/kdenetwork/kdepim/kdegames/ >> kdeadmin/kdeutils have cmake support. Now all compile completly for all is >> in progress. There are again some errors and missing module to test >> lib/header. >> >> For the moment I don't have report about compile test under Windows or >> MacOs so I don't know if it compiles fine. kdelibs compiles nearly complete with msvc (currently working on a simple mmap implementation for kdewin32 to fix makekdewidgets). the rest is untested on win32 afaik. >> >> I need some help to finish to port it. > > I won't be able to help much in the next days, I'll be at the Cebit for > KDE :-) Tomorrow too? > At least I'll try to write docs in the cmake wiki. > > Bye > Alex Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Status of cmake into kde
On Friday 10 March 2006 16:09, Laurent Montel wrote: > Hi, > I put a status of cmake into kde after this week. > Now > kdelibs/kdebase/kdetoys/kdeedu/kdeaccessibility/kdenetwork/kdepim/kdegames/ >kdeadmin/kdeutils have cmake support. Now all compile completly for all is > in progress. There are again some errors and missing module to test > lib/header. > > For the moment I don't have report about compile test under Windows or > MacOs so I don't know if it compiles fine. > > I need some help to finish to port it. I won't be able to help much in the next days, I'll be at the Cebit for KDE :-) At least I'll try to write docs in the cmake wiki. Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Status of cmake into kde
Hi, I put a status of cmake into kde after this week. Now kdelibs/kdebase/kdetoys/kdeedu/kdeaccessibility/kdenetwork/kdepim/kdegames/kdeadmin/kdeutils have cmake support. Now all compile completly for all is in progress. There are again some errors and missing module to test lib/header. For the moment I don't have report about compile test under Windows or MacOs so I don't know if it compiles fine. I need some help to finish to port it. Second question: do you think that we must create a "workspace" directory into kde module when it's specific linux (as in kdebase)? (for example for all applet ) Regards ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
