Project

General

Profile

--enable-cgribex vs --disable-cgribex

Added by Javier Lopez over 11 years ago

Hi,

My name is Javier López and I'm trying to help to bring to Ubuntu the best possible cdo package by default, I first became active in cdo because of:

https://code.zmaw.de/boards/1/topics/1171#message-1175

So there I saw Uwe Schulzweida recommended to compile cdo with the --enable-cgribex option, which seem to active the in-house support for grub1 files, however in another posts, such as:

https://code.zmaw.de/boards/1/topics/713#message-716

It's recommended to disable cgribex.

In ubuntu the cdo package is compiled with --disable-cgribex because of this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633934

Which in my opinion is wrong because cgribex only has to do with grub1 files, to support grub2 files cdo has to compile with grib_api

So, I wonder if it's better to leave it as it's now, or to change it and propose to change it in debian as well to compile it with --enable-cgribex by default.

Thanks in advance


Replies (2)

RE: --enable-cgribex vs --disable-cgribex - Added by Uwe Schulzweida over 11 years ago

Hi Javier,

The configuration default for GRIB1 in CDO is --enable-cgribex. This will use the internal CGRIBEX library to encode/decode GRIB1 messages. To support GRIB2 files CDO has to compile with grib_api, that's right! If CDO is configured with --disable-cgribex than the grib_api is also used to encode/decode GRIB1 files. But this feature is under construction and not tested. I would recommend to configure CDO with the CGRIBEX default (--enable-cgribex).

Cheers,
Uwe

    (1-2/2)