headers
Mike Jackson | 1 Nov 2007 01:57
Picon

Re: Detecting Mac OS X Version

Seans points are taken. Right now all I know is that if you are  
building on 10.5 then you need all this special linker crap due to  
the new linker in 10.5. I think I like the idea of parsing the  
"sw_vers" output better. Just need to implement it.

-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services

On Oct 31, 2007, at 7:41 PM, E. Wing wrote:

> I'm wondering the same about this topic. I think Sean might be right
> about checking for the SDK target version instead of OS X version,
> though I could come up with a contrived example where knowing the
> actual OS X version could be important, such as a CMake bug/issue you
> need to work around that only appears on 10.4.3 or something. So it
> would be good to have both.
>
> A warning about Darwin version checking...don't consider it a reliable
> indicator about which OS X version you are using. It is possible for a
> developer to upgrade Darwin independently from OS X. I remember seeing
> somebody do this before because they needed some feature that wasn't
> in the Apple shipping version. I think you should only check Darwin
> versions if you are actually dealing directly with Darwin.
>
> -Eric
> _______________________________________________
> CMake mailing list
> CMake@...
> http://www.cmake.org/mailman/listinfo/cmake
(Continue reading)

Permalink | Reply | 0 comments |
headers
James Bigler | 1 Nov 2007 05:25
Picon
Favicon

Re: Include path for a single file

Daniel wrote:
> James Bigler wrote:
>> I know you can add include paths for a single directory with 
>> INCLUDE_DIRECTORIES, but is it possible to set this for a single file 
>> with SET_SOURCE_FILES_PROPERTIES or by some other means?
>>
>> Thanks,
>> James
> 
> You could try:
> 
> SET_SOURCE_FILES_PROPERTIES(source_file PROPERTIES
>     COMPILE_FLAGS -I/include/path)

I was hoping for something a bit more portable, unless CMake magically 
understands -I/include/path and translates it for different compilers.

James
Permalink | Reply | 0 comments |
headers
Suhas Jain | 1 Nov 2007 08:23
Favicon

Building linux kernel module with Cmake

Hi All,

 

I am a newbie with cmake and am trying to build a Linux device driver with this utility.

I have tried this utility with building applications. It works fine. But, I am not able to compile the kernel modules.

I have a makefile for this driver which uses KBuild for compiling the driver and generates a .ko file.

Can anybody please help me?

 

Thanks in advance

 

 

 

_______________________________________________
CMake mailing list
CMake@...
http://www.cmake.org/mailman/listinfo/cmake
Permalink | Reply | 4 comments |
headers
Alexander Neundorf | 1 Nov 2007 10:05
Picon

Re: disabling the cache

On Wednesday 31 October 2007, Jesper Eskilson wrote:
> Bill Hoffman wrote:
> > For this case, you could have something like this:
> >
> > # if SOME_PROGRAM has a value but the program has been moved
> > # or removed from the system, then clear the cache entry
> > # so that find_program will try again.
> > if(SOME_PROGRAM AND NOT EXISTS ${SOME_PROGRAM})
> >   set(SOME_PROGRAM NOTFOUND CACHE FORCE "some program")
> > endif(SOME_PROGRAM AND NOT EXISTS ${SOME_PROGRAM})
> > find_program(SOME_PROGRAM myprog)
> >
> > So, if you know that you are changing a cmakelist file in a way that
> > requires something to be removed from the cache, just remove it, but be
> > careful not to remove it all the time.
>
> Ouch. My cmake files are unreadable enough without an added 3 lines here
> and there checking if the cache entry needs to be replaced or not.

With cmake cvs you could run "cmake -USOME_PROGRAM <dir>" which would remove 
the variable SOME_PROGRAM from the cache first and then run cmake.
But I guess that's no acceptable solution for MSVC users.

> BTW: Are there any plans of fixing the broken regeneration for Visual
> Studio? Or at least documenting it as known problem? As it is now, the
> project files are regenerated but not reloaded, and there is no feedback
> that the new project files aren't used for the build.

I really think this should be filed as a bug report/support issue/whatever the 
right way is to MS, so that they at least know about that (no matter whether 
they will find it worthwhile to fix something which will help writing 
portable software).

Alex
Permalink | Reply | 0 comments |
headers
Hendrik Sattler | 1 Nov 2007 10:29
Picon

Re: Building linux kernel module with Cmake

Am Donnerstag 01 November 2007 schrieb Suhas Jain:
> I am a newbie with cmake and am trying to build a Linux device driver
> with this utility.
>
> I have tried this utility with building applications. It works fine.
> But, I am not able to compile the kernel modules.
>
> I have a makefile for this driver which uses KBuild for compiling the
> driver and generates a .ko file.
>
> Can anybody please help me?

I don't see the point using cmake for such a task. Using Kbuild with a _very_ 
short Makefile (that never changes) and one Kbuild file, it's already simple 
enough. There is also no cross-platform support needed (it's going to be a 
linux kernel module anyway).

HS
Permalink | Reply | 3 comments |
headers
Jesper Eskilson | 1 Nov 2007 10:49
Picon
Gravatar

Re: disabling the cache

Andreas Pakulat wrote:
> On Mittwoch, 31. Oktober 2007, Jesper Eskilson wrote:
>> BTW: Are there any plans of fixing the broken regeneration for Visual
>> Studio? Or at least documenting it as known problem? As it is now,
>> the project files are regenerated but not reloaded, and there is no
>> feedback that the new project files aren't used for the build.
> 
> How exactly should cmake fix a bug in Visual Studio? As far as I 
> understood this thread the problem is that VS doesn't get that its 
> project files have changed and thus doesn't reload them. I suggest to 
> contact your MS support contact.

Visual Studio *does* reload the project files, but not *during* a build.
If any project files are modified during a build, they are reloaded
*after* the build is complete. I'm not sure if I would call this a bug,
even if it conjunction with cmake causes a breakage when cmake tries to
regenereate project files.

In any case, the automatic regeneration of project files *does* *not*
*work*, and my question was simply if there was a plan for either doing
something about it (such as disabling it per default, which would be a
sensible thing to do, IMHO), and/or documenting that it is broken.

--
/Jesper
Permalink | Reply | 7 comments |
headers
Suhas Jain | 1 Nov 2007 10:48
Favicon

RE: Building linux kernel module with Cmake

Thanks for you reply Hendrik
Even I know that Kbuild is a very simple procedure to do so.
But I have a source tree which has applications, drivers and other modules
for different OS as well as hardware architectures and I want to compile all
these folders from a single top level directory. All this can be achieved
with Cmake utlity. I have already compiled other modules. 
I want to know if it possible to use cmake for compiling kernel module

-----Original Message-----
From: cmake-bounces+suhasj=aftek.com@...
[mailto:cmake-bounces+suhasj=aftek.com@...] On Behalf Of Hendrik
Sattler
Sent: Thursday, November 01, 2007 3:00 PM
To: cmake@...
Subject: Re: [CMake] Building linux kernel module with Cmake

Am Donnerstag 01 November 2007 schrieb Suhas Jain:
> I am a newbie with cmake and am trying to build a Linux device driver
> with this utility.
>
> I have tried this utility with building applications. It works fine.
> But, I am not able to compile the kernel modules.
>
> I have a makefile for this driver which uses KBuild for compiling the
> driver and generates a .ko file.
>
> Can anybody please help me?

I don't see the point using cmake for such a task. Using Kbuild with a
_very_ 
short Makefile (that never changes) and one Kbuild file, it's already simple

enough. There is also no cross-platform support needed (it's going to be a 
linux kernel module anyway).

HS
_______________________________________________
CMake mailing list
CMake@...
http://www.cmake.org/mailman/listinfo/cmake
Permalink | Reply | 2 comments |
headers
Jesper Eskilson | 1 Nov 2007 10:51
Picon
Gravatar

Re: disabling the cache

KSpam wrote:

> All of my coworkers use Visual Studio 2005, and it properly indicates when 
> project files need to be reloaded.  In fact, it is quite an annoyance when 
> you have dozens of project files that are modified by CMake, and you have to 
> manually say "Yes" to reloading each and every one of them.  Of course, this 
> is no fault of CMake, as its job is to simply generate the project files.  I 
> would like to see Visual Studio handle reloading project files a little more 
> eloquently.

Yes, I agree. But still, VS8 actually reloads all projects which is more
than you can say about VS7 which only reloaded the first project. :-)

> 
> This sounds to me like a specific setting on your Visual Studio install.  I 
> believe that there is a setting in Visual Studio that can ignore externally 
> modified files or automatically reload them.  Perhaps you are unknowingly 
> using this setting.

As I said in a previous post, the project files are being reloaded, but
not until *after* the build is complete. (Unless Visual Studio silently
reloads projects during a building, but I seriously doubt that.)

--
/Jesper
Permalink | Reply | 5 comments |
headers
Josef Karthauser | 1 Nov 2007 11:59
Favicon

Make clean - doesn't clean dependencies.

It doesn’t appear that a ‘make clean’ in a subdirectory of the build tree cleans any of the dependencies.  Does anyone know of a way that it can be persuaded to?

 

Joe

_______________________________________________
CMake mailing list
CMake@...
http://www.cmake.org/mailman/listinfo/cmake
Permalink | Reply | 1 comment |
headers
Andreas Pakulat | 1 Nov 2007 12:06
Picon
Picon
Gravatar

Re: disabling the cache

On 01.11.07 10:49:12, Jesper Eskilson wrote:
> In any case, the automatic regeneration of project files *does* *not*
> *work*, and my question was simply if there was a plan for either doing
> something about it (such as disabling it per default, which would be a
> sensible thing to do, IMHO), and/or documenting that it is broken.

So far you're the only one claiming that (in this thread), I suggest to
come up with a small sample project where changing the CMakeLists.txt
doesn't trigger a cmake run. If you've got that you can file a bugreport
against cmake.

Andreas

--

-- 
You are a bundle of energy, always on the go.
Permalink | Reply | 6 comments |

Gmane