AW: [certi-dev] Question about NextEventRequest Service

[Roth, Christoph]

Hi Eric,

shame on me:) I didn't use the CVS version but the 3.4.0-Version that is 
available here: http://download.savannah.gnu.org/releases/certi/beta/

Now that I tried the CVS Version it seems to work and is much much faster than 
before. Thank you for the hint, was very helpful.

Now I try to setup a testcase.

Regards,
Christoph


Karlsruher Institut für Technologie (KIT)
Institut für Technik der Informationsverarbeitung (ITIV)
 
Dipl.-Ing. Christoph Roth
 
Vincenz-Prießnitz-Str. 1, Geb. 07.07, Raum 202
76131 Karlsruhe
Telefon:+ 49 721 - 608 - 2880
Telefax:+ 49 721 - 608 - 2511
 
address@hidden
www.kit.edu http://www.itiv.kit.edu/
 
KIT - Universität des Landes Baden-Württemberg und
nationales Großforschungszentrum in der Helmholtz-Gemeinschaft


-----Ursprüngliche Nachricht-----
Von: address@hidden [mailto:address@hidden Im Auftrag von Eric Noulard
Gesendet: Dienstag, 2. November 2010 17:01
An: CERTI development discussions
Betreff: Re: [certi-dev] Question about NextEventRequest Service

2010/11/2 Roth, Christoph <address@hidden>:
> Hi Eric,
>
> I tried
>
> cmake -DMAKE_INSTALL_PREFIX=/home/roth/certi-3.4.0 
> -DCERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL=ON ../CERTI-3.4.0cvs-Source
>
> as well as
>
> cmake -DMAKE_INSTALL_PREFIX=/home/roth/certi-3.4.0 
> -DNULL_PRIME_MESSAGE_PROTOCOL=ON ../CERTI-3.4.0cvs-Source
>
> but the behavior is the same. The tick2 function still has a delay of several 
> seconds if the NMR parameter has a high value.
>
> Both parameters are also not visible in the cmake gui? Are they correct?


The parameter is:
CERTI_USE_NULL_PRIME_MESSAGE_PROTOCOL

it is at line 73 of certi/CMakeLists.txt (of current CERTI cvs version)

you should see it in the CMake GUI.

ar e you sure you have an up to date CERTI cvs tree?

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

-- 
CERTI-Devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/certi-devel