Re: [certi-dev] CERTI Windows build

[Eric Noulard]

2011/9/16 Jan-Patrick Osterloh <address@hidden>:
> Am 15.09.2011 18:35, schrieb Eric Noulard:
>> 2011/9/15 Jan-Patrick Osterloh <address@hidden>:
>>> Dear all,
>>>
>>> I tried to compile the current version of the CVS version of CERTI on
>>> windows with mingw. My plan is to setup a nightly build once it is
>>> working with a fresh checkout. I personally use a fixed version from
>>> Christoph Läsche.
>>>
>>> Right now, I have the following compile problems:
>> Jean Phillippe LEBEL from forward is interested in a working [out of
>> the box] windows build of CERTI.
>> May be with MSVC instead of mingw but, I think there are mostly common 
>> issues.
>>
>> Please |re-]read this ML thread:
>> http://lists.nongnu.org/archive/html/certi-devel/2011-09/msg00002.html
>>
>> and bug/patched refered therein:
>> http://lists.nongnu.org/archive/html/certi-devel/2011-09/msg00006.html
> Ok, I read from this that I should apply the three patches you mention
> below.

Not really.
Because they are not OK.
You may read the comments and try some of the patches in order
ro improve them and make them works for you.

Those patches are "unfinished work".

>> what is the auto-import feature?
>
> See: http://gnuwin32.sourceforge.net/compile.html - Auto-import section.
> I don't know if we need to fix this.

I'll read that, thanks.
>>> What shall I do now? Do you have a patch for this (at least I remember
>>> something like a patch for FedTime??)?
>> Yes there is some:
>> https://savannah.nongnu.org/patch/?7566
>> https://savannah.nongnu.org/patch/?7569
>> https://savannah.nongnu.org/bugs/?30003
>
> Ok, I started with
>
> https://savannah.nongnu.org/patch/?7566
>
>
> I downloaded the file and stored it to my certi folder. The I'd tried to
> run "patch -i fedtime_windows.patch". This resulted in the following
> output:
> patching file `CMakeLists.txt'
> Hunk #1 FAILED at 91.
> Hunk #2 FAILED at 151.
> 2 out of 2 hunks FAILED -- saving rejects to CMakeLists.txt.rej. I
> attached CMakeLists.txt.rej.
>
> What I'm doing wrong? Sorry, but I'm not so familiar with CVS (we are
> using SVN internally) and "patch".

You process is OK but this patch wasn't built against current CVS HEAD
so when this happen you have to edit the patch file itself with an editor
identify the changes and report them in the updated code by hand.

I have just done this for thiis one.
You'll have to have a look for the two remaining patches.

>> I'm sure we can end-up with something satisfactory for both Windows
>> and Linux (or other unices).
>> Once we are in that state we can setup systematic build
>> http://lists.nongnu.org/archive/html/certi-devel/2008-10/msg00028.html
>> in order to avoid breaking the Windows build again.
> This dashboard thing looks interesting. I'm willing to setup something
> that performs a nightly build on windows, with mingw. In fact we are
> already doing something like this for our own software, and I'd like to
> extend it with a CERTI nightly build. Does this CDash means, I simply
> have to call "ctest --overwrite Site="OFF" -D Nightly", and the rest is
> done automatically?

That's the idea.
But I'll start another thread on the cdash with CERTI subject.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org