>> And I am allergic to Windows, so there will need to be a "CMake on Windows"
>> champion to step up and take this bull by the horns.
>>
>
> Good luck finding that one :)
>
Not my job. I don't use Windows. But I think the folks that do have
found their champion. :)
>
>
> I found
Michael Bruck wrote:
> I tried that and it seems IS_CYGWIN is not set correctly on cygwin. Any idea ?
>
> Michael
>
Michael,
I see a potential solution that is worth a try.
Move these lines:
if(CYGWIN)
set(IS_CYGWIN, true)
else(CYGWIN)
set(IS_CYGWIN, false)
endif(CYGWIN)
if(MINGW)
On Wed, Apr 29, 2009 at 5:08 PM, Dick Hollenbeck wrote:
> How do you build openocd on windows, does it require CYGWIN or is there
> another way?
MinGW and cygwin should work, not sure if there are other ways to compile it.
> Using CMake on Windows, a reasonable goal would be to ween ourselves of
> I tried that and it seems IS_CYGWIN is not set correctly on cygwin. Any idea ?
>
> Michael
>
>
Michael,
Thanks for trying this.
How do you build openocd on windows, does it require CYGWIN or is there
another way?
Using CMake on Windows, a reasonable goal would be to ween ourselves of
I tried that and it seems IS_CYGWIN is not set correctly on cygwin. Any idea ?
Michael
On Tue, Apr 28, 2009 at 10:52 PM, Dick Hollenbeck wrote:
> Igor Skochinsky wrote:
>>
>> Hello Dick,
>>
>> Tuesday, April 28, 2009, 7:29:46 PM, you wrote:
>>
>> DH> Latest.
>> DH> Paaleese commit any time.
>>
Igor Skochinsky wrote:
Hello Dick,
Tuesday, April 28, 2009, 7:29:46 PM, you wrote:
DH> Latest.
DH> Paaleese commit any time.
JFYI, it seems you forgot CMakeModules/* .
Thank you sir. My oops. Fix attached.
Here is my script to generate this patch now. I was missing the
src/CMakeModul
Latest.
Paaleese commit any time.
Thanks,
Dick
Index: src/pld/CMakeLists.txt
===
--- src/pld/CMakeLists.txt (revision 0)
+++ src/pld/CMakeLists.txt (revision 0)
@@ -0,0 +1,11 @@
+# Copyright 2009 SoftPLC Corporation http://softp
On Apr 17, 2009, at 7:03 AM, Dick Hollenbeck wrote:
Piotr Esden-Tempski wrote:
Hi!
On Apr 17, 2009, at 4:52 AM, Dick Hollenbeck wrote:
There still needs to be some
if(APPLE)
endif(APPLE)
lines added for static libraries on APPLE.
These should be called MACOS_X as Apple is a company,
Piotr Esden-Tempski wrote:
> Hi!
>
> On Apr 17, 2009, at 4:52 AM, Dick Hollenbeck wrote:
>
>>
There still needs to be some
if(APPLE)
endif(APPLE)
lines added for static libraries on APPLE.
>>>
>>> These should be called MACOS_X as Apple is a company, not a product
Hi!
On Apr 17, 2009, at 4:52 AM, Dick Hollenbeck wrote:
There still needs to be some
if(APPLE)
endif(APPLE)
lines added for static libraries on APPLE.
These should be called MACOS_X as Apple is a company, not a product
or
OS.
You are correct. CMake probably has its own platform def
>> There still needs to be some
>>
>> if(APPLE)
>> endif(APPLE)
>>
>> lines added for static libraries on APPLE.
>>
>
> These should be called MACOS_X as Apple is a company, not a product or
> OS.
You are correct. CMake probably has its own platform define however,
that it defines automagicall
On Apr 16, 2009, at 6:57 PM, Dick Hollenbeck wrote:
This is a comprehensive patch.
A number of problems were fixed.
It builds basically *all* the possible drivers now, and support
static libraries for libusb and libftdi. The only one that gave me
grief is ecosboard, but I think that requ
This is a comprehensive patch.
A number of problems were fixed.
It builds basically *all* the possible drivers now, and support static
libraries for libusb and libftdi. The only one that gave me grief is
ecosboard, but I think that requires some headers not present?
There still needs to be
Michael Schwingen wrote:
> Dick Hollenbeck wrote:
>
>> I am not a CMake expert, but this is a decent first draft. I believe
>> it will be possible to get to a point where you can build openocd just
>> with simple tools on Windows, no need for CYGWIN or even a bash shell
>> script.These scri
Dick Hollenbeck wrote:
>
> I am not a CMake expert, but this is a decent first draft. I believe
> it will be possible to get to a point where you can build openocd just
> with simple tools on Windows, no need for CYGWIN or even a bash shell
> script.These scripts have been tested on Linux with
Kishore,
Thank you for your efforts to make this usable by those who would.
Attached is a single comprehensive patch, which should be used instead
of my two previous patches.
For those who would like to give it a spin, remember to use an out of
source build, and to use the "ccmake" command
On Tuesday 14 Apr 2009 7:22:38 am Dick Hollenbeck wrote:
> Index: src/helper/CMakeLists.txt
> ===
> --- src/helper/CMakeLists.txt (revision 0)
> +++ src/helper/CMakeLists.txt (revision 0)
> @@ -0,0 +1,27 @@
> +# Copyright 2009 Sof
Øyvind Harboe wrote:
> I am not very keen on changing anything in terms of
> tools around openocd as there are a lot of developers out
> there that are familiar with the current situation. Every so
> often we get a request to use some new tool, switch version
> control, etc. I believe that it is a
Nico Coesel wrote:
> Here is another grazy idea regarding build tools: how about adding
> Eclipse project definitions? From experience I know that Eclipse
> projects can be transferred between Windows and Linux without problems.
>
> I agree the autotools aren't ideal especially when cross-compiling
lists.berlios.de
> [mailto:openocd-development-boun...@lists.berlios.de] Namens
> Dick Hollenbeck
> Verzonden: dinsdag 14 april 2009 14:02
> Aan: Openocd-Dev
> Onderwerp: [Openocd-development] [PATCH] Cmake part 2
>
>
> This adds
>
> config.h.cmake
>
>
This adds
config.h.cmake
which was missing in the first patch.
It seems that I will need help getting this committed.
CMake fans please step forward and make your voices heard. CMake has been accused of being off the beaten path.
From my perspective, those that take the auto
On Tuesday 14 Apr 2009 7:22:38 am Dick Hollenbeck wrote:
> +if(RELEASE)
> +set(RELSTR Release)
> +set(PKGBLDREV "")
> +else(RELEASE)
> +set(RELSTR svn:)
> +find_package(Subversion)
> +if(Subversion_FOUND)
> +subversion_wc_info( ${PROJECT_SOURCE_DIR} OPENOCD )
> +
I am not very keen on changing anything in terms of
tools around openocd as there are a lot of developers out
there that are familiar with the current situation. Every so
often we get a request to use some new tool, switch version
control, etc. I believe that it is a good thing that any such
switc
See Dick make CMake files.
Can you CMake any sense of this?
http://www.vtk.org/Wiki/CMake_FAQ
I find it easier to get work done in CMake than in any other build
system that I have used.
I am not a CMake expert, but this is a decent first draft. I believe it
will be possible to get t
24 matches
Mail list logo
