Re: [CMake] *Updated* Eclipse CDT4 CMake Generator - Pre-Alpha version
I think having the last 2 versions is a good idea... that way if the latest and greatest gets a bad bug in it, there is a way to back down to the previous version Miguel A. Figueroa-Villanueva [EMAIL PROTECTED] 4/08/2007 2:19 a.m. On 8/3/07, Eric Noulard wrote: 2007/8/3, Bill Hoffman : So, I don't want to fill the disk with these things. Should I just remove the previous night, or maybe only put them out every two weeks? I would say that keeping the last 2 successful builds should be more than enough for (my) currently forseen usage. I don't use or need daily snapshots since I update and compile through cvs, but I agree that it should be *daily* snapshots and buffer them as you see fit... 2 is already 2 more than I need anyway ;) --Miguel ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] cmake support Dev C++
Brandon (and everyone else reading this), I fear you misunderstood something from my last message, when you said CMake's level of Java support is a strategic risk. Eclipse isn't just a cross-platform crowd, it's a cross-platform heavily Java crowd. What I meant was that we need as good as possible integration between cmake and the eclipse CDT. As I am sure you are aware, the CDT is 100% C++, and has nothing to do with Java. Regarding Eclipse in a more general sense so we are all clear, I want to get one possible misconception out of the way... While the Eclipse platform was primarily written using Java, the eclipse platform should by no-means a Java IDE. Forgive me if you know about all this already... but I am sure there are other C++ folks here that are not aware of the background. Think of it this way: How can you call Eclipse an IDE if it does not include a compiler? In other words, how can it be an Integrated Development Environment, if it doesn't come with everything you need to actually use it? What the Eclipse platform really IS though, is a great platform for making IDEs. One great example of an IDE written using the Eclipse platform is the Eclipse Java IDE, which is arguably the most popular Java IDE around. Of more interest to this group though, I assume are C/C++ IDEs. Besides the Eclipse C/C++ IDE (CDT) 4.0 which I mentioned before, there are number or open source and or commercial C++ IDEs built using the Eclipse Platform including: Nokia Carbide C++ IDE Wind River Workbench LynuxWorks Luminosity QNX Momentics ACCESS Linux Platform Development Suite Mentor Graphics EDGE Developer Studio Telelog Tau Hi-tech Hi-Tide Now you might ask: why does this matter? Or Why are you telling us all this? The point I am making is that if a cmake plugin plays well with the Eclipse CDT IDE and makes C++ development easier, we get exposure to the potential userbase automatically for all those other C++ IDEs listed above as well automatically, as they are built on top of the Eclipse platform. So, to make a long story short, don't worry about the java crowd. This is all about C/C++ :) Cheers, Ding. Brandon Van Every [EMAIL PROTECTED] 31/07/2007 2:22:56 a.m. On 7/30/07, Andy Dingfelder [EMAIL PROTECTED] wrote: Personally, my motivation is that I want to use Eclipse on Linux to develop both java and c++ apps, and want them to run on mac, Linux and PC. I have seen multiple discussions in a variety of places that talk about how to do this, some with better luck than others. I see cmake as a natural fit for Eclipse as (IMHO) Eclipse is perhaps the most widely used *multi-platform* environment out there, running on basically any OS that java runs on, and everyone here knows the strengths of cmake, so I don't need to expand upon that. CMake's level of Java support is a strategic risk. Eclipse isn't just a cross-platform crowd, it's a cross-platform heavily Java crowd. So if CMake's Java support is irritating to work with, that could put off Eclipse tool developers, whatever CMake's C/C++ merits are. On the other hand, getting one's feet wet with Eclipse and Java would be a good way to drive the improvement of CMake's Java support. I would just anticipate a lot of bumps, and invitations to substantial work. I do think that light would ultimately be seen at the end of the tunnel, however. Code::Blocks doesn't have any Java encumbrance, it's a C/C++ developer crowd. Of course it doesn't have nearly the number of users as Eclipse, nor the commercial acceptance and clout, so that's a strategic risk. I think someone would have to either be a Code::Blocks diehard and really want to get it done, or else it would have to be relatively easy to do. Otherwise, nobody would bother. Another risk with Code::Blocks is their release policy is immature. They might have great stuff, but they can't seem to manage to put an official binary distribution out there. Instead one does this daily snapshot download dance, grabbing 3 different files. It suggests to me that their architecture could be in flux, which could make CMake support a moving target. Chasing a handful of devs that don't really value release maturity or commercial stability might be no fun at all. But I don't actually know their culture or the relative stability of their code, so I won't pass judgment. Be sure to research it before diving in though. The Eclipse community is very mature as far as their release policies. Cheers, Brandon Van Every ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender
Re: [CMake] cmake support Eclipse
What's a non-trivial Java app that's using a CMake build? Dart2 server perhaps? I don't know any java apps that are built using cmake if thats what you mean. Building java apps it typically done using Maven or Ant, and I see no need to re-invent the wheel and use cmake to do that. All cmake needs to do to meet my needs is build C++ code, which it does very well from what I have seen. CMake only has to be elegant enough to address the needs of a CDT implementor. Which might be substantial, actually, I don't know. Eclipse is a big project. I do not see what the size of eclipse has to do with how cmake would work. The point I was making before is that the implementor who tries to integrate cmake into CDT would treat it the same way that the maven plugin developers treated maven... They made the plugin use the build system as is instead of trying to make it fit Eclipse, so that builds done from within the IDE could also still be done from the command line. In the same sense, I do not think cmake should change to meet Eclipse's needs, therefore the elegance of cmake is not the question. If cmake becomes more elegant, so much the better, but it should not be done to make the CDT better, it should be done for cmake as a whole. My vision for a cmake plugin would be as an administrative tool that eases the creation of the CMakeLists.txt file and the running of ccmake. Basically, there would be a GUI screen or wizard that would ask questions such as what OS you want to target, what files to include, and what toolchain to use, and then you could simply tell eclipse to do a build and it would use cmake to build all the appropriate targets. WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] cmake support Dev C++
I personally think that the Eclipse CDT might be a good option to explore instead of focusing on other smaller, less used IDEs. The Eclipse userbase is huge and the CDT portion is growing with leaps and bounds, especially in the embedded and cross platform areas. It seems to me that the tighter that cmake could integrate into eclipse, the larger the cmake userbase would grow, much in the same way that eclipse has adopted the Maven build system in the Java community. Thoughts from any other Eclipse users out there? Hendrik Sattler [EMAIL PROTECTED] 26/07/2007 6:50:20 p.m. Zitat von protein [EMAIL PROTECTED]: Since Dev C++ is a nice free IDE in windows and is developing rapidly. Is it possible that one day cmake will support Dev C++ project file generation? Probably not unless you write such a generator. The youngest entry in devcpp CVS is 23 month old and the 4.9.9.2 beta release is probably not getting an update, anymore, but it not very stable. The v4 version as an alternative download is close to unusable, too. Not too many chances, I'd say. Some suggest CodeBlocks instead but what shall be the impression of a software that is _only_ available via CVS because its authors do not dare to make a release :-/ I'd suggest to use VCexpress as editor and compile on command line. HS ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] cmake support Dev C++
Brandon, I hear what you are saying loud and clear, and agree pretty much with what you are saying. As you alluded to, my query was simply a way of finding out the current state of things, and I very well my get my A into G and organize some work around improving the integration between cmake and eclipse. What I don't want to do though is reinvent the wheel. I do think it is important to learn from others past mistakes and success stories and I value any experiences like this that you and others can share. Getting back to my vision for how cmake *could* work better, I find myself comparing cmake to maven. In this case, maven is a widely used mature tool for doing (java) builds and was not integrated (or at least not very well) into eclipse. I very good team of volunteers has spent a lot of time developing an eclipse plugin for maven2 and it is now a huge success. What they did NOT do is tie maven to eclipse. What I mean by this is that Eclipse uses maven but does not drive the overall maven strategy or functionality, as maven is a huge success on it's own, via the command line, much as cmake is. Why am I worrying about eclipse (plugin) integration? To put things into perspective, there were over 1.3 million downloads of eclipse in the first 30 days eclipse 3.3 was available. What I do not know is how many users downloaded the C++ CDT system (I assume hundreds of thousands). I have asked this question but have not gotten a response yet. Personally, my motivation is that I want to use Eclipse on Linux to develop both java and c++ apps, and want them to run on mac, Linux and PC. I have seen multiple discussions in a variety of places that talk about how to do this, some with better luck than others. I see cmake as a natural fit for Eclipse as (IMHO) Eclipse is perhaps the most widely used *multi-platform* environment out there, running on basically any OS that java runs on, and everyone here knows the strengths of cmake, so I don't need to expand upon that. I look forward to hearing your ideas and thoughts on this topic. Cheers, Ding Brandon Van Every [EMAIL PROTECTED] 30/07/2007 3:29:07 p.m. On 7/29/07, Andy Dingfelder [EMAIL PROTECTED] wrote: I personally think that the Eclipse CDT might be a good option to explore instead of focusing on other smaller, less used IDEs. Well, yeah, like, duh. Thoughts from any other Eclipse users out there? But there's this funny thing about open source. It's not about thoughts. It's about actions that actual people choose to undertake. And they do it for their own reasons. Whatever turns them on, or whatever makes them money. If a Code::Blocks individual or group up and decides they're gonna make Code::Blocks support for CMake, hey presto, suddenly you have Code::Blocks support. If an Eclipse individual or group gets a wild hair, hey presto, Eclipse support. What doesn't exist, however - and I think sometimes people make this mistake, which is why I'm saying this - is some kind of labor pool that just goes and implements stuff because it would be a good idea. That's somewhat true in the proprietary commercial world, but no open source volunteer works that way. Thus from the standpoint of people who will actually do the work, it has nothing to do with whether Code::Blocks is more or less advisable than Eclipse. I chose to make a great CMake build for the Chicken Scheme compiler. I did it because open source builds are a sorry state of affairs on Windows. It just seriously bugs me, and I don't think I should have to defect to Linux or swallow the FSF kool-aid to see quality engineering. I don't know if there are even 100 people in the world who care about what I have written. But a few people do care, and I know that unlike most of the other open source builds out there, mine definitely doesn't suck. I made $0 on this. I did it for purely ideological reasons, not what was advisable. In fact, I was so ideological that I almost got evicted twice while pursuing the work! That got old; thankfully, now I'm making money on my CMake skills so honed. So there's poetic justice in where I'm at now. But sensible allocation of resources had nothing to do with why I got started, or why I stuck with it for a man-year. In fact, I daresay anyone sensible would just go get a real job and never bother! Like, one of those proprietary corporate jobs where some manager tells a bunch of underlings what's most advisable and where they're going to put their development energies for the next 6 months. I don't want to be too harsh on an innocent query. Soliciting people's interest is often a 1st step in organizing. Action is what counts though. The only way to lead in open source, is by example. Generally speaking, you can't tell open source people what to do. They do what they're inspired to do, because usually there isn't any other reward for it. Cheers, Brandon Van Every ___ CMake mailing list
Re: [CMake] cmake 2.6
Great. I will try and see about getting the latest version. Is anyone here running Gentoo? The way I got cmake 2.4 was by running emerge, and clearly that is not going to work with the cvs builds. So, I assume I need to set up a portage overlay for emerging a development version but I would rather not reinvent the wheel. Thoughts? David Cole [EMAIL PROTECTED] 25/07/2007 10:46:36 p.m. From the CMake CVS repository. CVS HEAD has the cross-compiling functionality in it right now... HTH, David On 7/24/07, Andy Dingfelder [EMAIL PROTECTED] wrote: The example on http://www.cmake.org/Wiki/CMake_Cross_Compiling says that this is supported by CMake starting with version 2.6.0 (not yet released as of July 2007). Where can one download v2.6 to try this ? WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] cmake 2.6
The example on http://www.cmake.org/Wiki/CMake_Cross_Compiling says that this is supported by CMake starting with version 2.6.0 (not yet released as of July 2007). Where can one download v2.6 to try this ? WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] need help with modified helloworld
I'm wondering if someone could help me with a simple change to the helloworld example I have gotten the helloworld to work with either windows output or linux output, by changing the base CMakeLists.txt file but am struggling on how to build both the current example is set up as follows: CMakeExample/Hello CMakeExample/Demo CMakeExample/Build CMakeExample/CmakeLists.txt My goal is to set up my system something like this: CMakeExample/src/Hello CMakeExample/src/Demo CMakeExample/lib -- not sure if I need this? CMakeExample/linuxBuild/CmakeLists.txt CMakeExample/windowsBuild/CmakeLists.txt It seems that the only difference between the CmakeLists.txt file for linux and windows is that the windows one has SET(CMAKE_C_COMPILER i686-mingw32-gcc) SET(CMAKE_CXX_COMPILER i686-mingw32-g++) while the linux one uses the default basically I want the helloworld example but running out of source directory thoughts? WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: RE [CMake] Eclipse CDT and CMake
Hi Mike, No problem at all... the vast majority of your tutorial is spot on, and only a couple of small issues caused me any confusion at all. I am familiar with make files in general and eclipse, but this is my first exposure to cmake and hopefully my questions will help other newcomers. My goal here is cross platform development under eclipse and I figured cmake was the best way to attack this. I have gotten the basic hello world from the cmake examples download to successfully compile from eclipse and am at this point trying to get it to generate both a windows exe and linux executable. Here are a couple of simple suggestions that might help: 1. you might want to add some step numbers to the instructions, so people can refer to step 3 in questions etc. 2. when updating your wiki, on the page where you Select the MakeFile Project type, choose Other Toolchain and click Next if they expand the node entitled makefile project and choose Hello World C++ Project, eclipse will create the cpp file. 3. for people new to cmake, an example CMakeLists.txt would be quite useful. Thanks a bunch for the great tutorial other than that. Cheers, - Ding Mike Jackson [EMAIL PROTECTED] 24/07/2007 3:05:05 p.m. Andy, sorry for the problems that you had trying to follow my instructions. Let me address some of your troubles. 1] The CMake Editor plugin is just that.. A plugin for Eclipse that will do syntax coloring and some code completion for CMake commands in CMake files (CMakeLists.txt and *.cmake). This plugin does NO project management at all. Let me repeat.. This plugin will do NO Project management of either CMake files or Eclipse CDT projects. When I wrote the tutorial I assumed some knowledge of CMake and how it works and was aimed at those that wanted to use CMake in conjunction with Eclipse. Maybe I should have stated that on the Wiki.. 2] The MyProject Example is just a placeholder. There really is not any example. I was just using this as an example of how to layout a project. Again, I assumed that the reader already had a project and was wanting to use that existing project with CMake and Eclipse. This probably was not a good assumption. In Hind sight I should have used an example from the actual CMake distribution. I will try and update the wiki to use this example instead, hopefully making things more clear. 3] Why am I running ccmake from the comand line? A clean project that is based on CMake typically will NOT have any type of Makefile ready to go. That is the point of CMake, to auto-generate Makefiles (or other platform specific project files) from the CMakeLists.txt file (and other supporting *.cmake files). So by default Eclipse has no idea what to do with a CMake based project. Also not that when setting up the project in Eclipse you need to select the Makefile based project as _you_ will be providing Makefiles, generated by CMake, to Eclipse CDT to use for the build process. By running ccmake or cmake (your choice) from the command line before setting too many things in Eclipse, Eclipse will complain less or not at all when you set up your project. This is kind of boot strapping the process a bit as there is no real integration of CMake with Eclipse. The integration is that Cmake will generate and keep up to date the makefiles that Eclipse will use for its build. I hope that helps explain some things. If I get some time on Tuesday, I will rewrite parts of the Tutorial to use the Example that comes with CMake instead of my own virtual example. Again, I am sorry for the troubles that you may have had with my instructions/tutorial. Keep asking questions and the community will try to help answer them. Respectfully Mike Jackson WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of Landcare Research. SirTrack http://www.sirtrack.com ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
