mirror/netcdf-c
2
0
Fork 0
mirror of https://github.com/Unidata/netcdf-c.git synced 2024-12-27 08:49:16 +08:00
Code Issues Packages Projects Releases Wiki Activity
bab5ef7549
netcdf-c/ncgen/Make0

61 lines
1.3 KiB
Plaintext
Raw Normal View History

close Jira NCF-154
2012-03-08 07:38:51 +08:00
# Test c output
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
T=t
K=4
L=-L5
close Jira NCF-154
2012-03-08 07:38:51 +08:00
#VG=valgrind --leak-check=full
[NCF-267]/SAI-630695 Add support for embedded NUL characters in character arrays and added some test cases. Note that embedded NULs in netcdf-4 string constants are still illegal. This is because strings are not counted in the netcdf API, so they are implicitly NUL terminated.
2013-09-24 07:08:50 +08:00
STDLIB=/usr/local
#STDLIB=/share/ed/local/${HOST}
Added code to support NIL values for strings in ncgen. Needs test cases.
2013-07-11 04:00:48 +08:00
Added NIL tests
2013-07-11 04:53:50 +08:00
CFLAGS=-I../include -I${STDLIB}/include
LDFLAGS=../liblib/.libs/libnetcdf.a -L${STDLIB}/lib -lhdf5_hl -lhdf5 -lz -lm -lcurl
# -lcurl -lm -llber -lldap -lrt -lssl -lcrypto -ldl
close Jira NCF-154
2012-03-08 07:38:51 +08:00
CLASSPATH=".:ncCore-4.2.jar"
btest::
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
./ncgen ${L} -$K -lb -o ${T}.nc ${T}.cdl
../ncdump/ncdump -L2 ./${T}.nc >${T}.dmp
close Jira NCF-154
2012-03-08 07:38:51 +08:00
diff -wBb ${T}.cdl ${T}.dmp
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
rm -f ./junk.nc
../ncdump/nccopy ./${T}.nc ./junk.nc
close Jira NCF-154
2012-03-08 07:38:51 +08:00
ctest::
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
./ncgen ${L} -$K -lc ${T}.cdl >${T}.c
close Jira NCF-154
2012-03-08 07:38:51 +08:00
gcc -o ${T} ${CFLAGS} ${T}.c ${LDFLAGS}
./${T}
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
../ncdump/ncdump ${L} ./${T}.nc >${T}.dmp
close Jira NCF-154
2012-03-08 07:38:51 +08:00
diff -wBb ${T}.cdl ${T}.dmp
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
rm -f ./junk.nc
../ncdump/nccopy ./${T}.nc ./junk.nc
close Jira NCF-154
2012-03-08 07:38:51 +08:00
Added the necessary code to support group renaming. The primary API is 'nc_rename_grp(int grpid, const char* name)'. No test cases provided yet. This also required adding a rename_grp entry to the dispatch tables.
2013-07-20 05:48:37 +08:00
gtest::
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
./ncgen -$K -lc ${T}.cdl >${T}.c
Added the necessary code to support group renaming. The primary API is 'nc_rename_grp(int grpid, const char* name)'. No test cases provided yet. This also required adding a rename_grp entry to the dispatch tables.
2013-07-20 05:48:37 +08:00
gcc -g -O0 -o ${T} ${CFLAGS} ${T}.c ${LDFLAGS}
gdb --args ./${T}
vctest::
1. [NCF-276]/XXI-796914 Columbia server does not serve up proper opendap DDS replies. The Dataset {...} name changes depending on if the request has certain kinds of constraints. Code for a hack was not being used, so restore it. The fix is to effectively ignore differences in Dataset node names if the code is coming from columbia.edu. 2. [NCF-278] The ncgen code is improperly typing int64 integer constants as uint64. 3. [NCF-279] Empty string constants were not being properly filled when their target array is length 1 or more.
2013-11-18 05:26:14 +08:00
gcc -c ${CFLAGS} ${T}.c
gcc -o ./vt ${T}.o ${LDFLAGS}
${VG} ./vt
close Jira NCF-154
2012-03-08 07:38:51 +08:00
[NCF-265] Ncgen is unable to resolve ambiguous references to an enum constant when two different enums have same econstant name. Solved by allowing more specific forms for econstant references. 1. /.../enumname.enumconstname 2. enumname.enumconstname 3. enumconstname Case 1 is resolved by using the econstant in the specific enum definition. If none is found, an error is reported. Case 2 is resolved by 1. finding an enclosing group with an enum definition with the specified name and containing the specified econstant. If there are more than one, then an error is reported 2. finding all enum definitions in the dataset that have the specified enum name and contain the specified econstant. If more than one is found, then an error is reported. If the above two methods fail, then report an error. Case 3 is similar to case 2, but all enums, irrespective of name are used if they contains the specified enum constant. The ref_tst_econst.cdl test in ncdump is causing ncdump to fail. So there may be yet some problem.
2013-09-21 10:31:21 +08:00
ftest::
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
./ncgen -$K -lf77 ${T}.cdl >${T}.f77
[NCF-265] Ncgen is unable to resolve ambiguous references to an enum constant when two different enums have same econstant name. Solved by allowing more specific forms for econstant references. 1. /.../enumname.enumconstname 2. enumname.enumconstname 3. enumconstname Case 1 is resolved by using the econstant in the specific enum definition. If none is found, an error is reported. Case 2 is resolved by 1. finding an enclosing group with an enum definition with the specified name and containing the specified econstant. If there are more than one, then an error is reported 2. finding all enum definitions in the dataset that have the specified enum name and contain the specified econstant. If more than one is found, then an error is reported. If the above two methods fail, then report an error. Case 3 is similar to case 2, but all enums, irrespective of name are used if they contains the specified enum constant. The ref_tst_econst.cdl test in ncdump is causing ncdump to fail. So there may be yet some problem.
2013-09-21 10:31:21 +08:00
gfortran -c ${CFLAGS} ${T}.f77
close Jira NCF-154
2012-03-08 07:38:51 +08:00
jtest::
Fix for Github issue 314. Problem was in oc2/dap.y. In definition of errormsg:, change WORD_WORD to WORD_STRING since the msg field of an opendap error response is a quoted string. Also took the opportunity to modify ncgen to transfer the logging level (-L flag) into the c-code generated using -lc.
2016-09-02 12:06:07 +08:00
./ncgen -$K -lj ${T}.cdl >Main.java
close Jira NCF-154
2012-03-08 07:38:51 +08:00
javac -d . -classpath "${CLASSPATH}" Main.java
# java -cp ${CPATH} ./${T}
# ../ncdump/ncdump ./${T}.nc >${T}.dmp
# diff -wBb ${T}.cdl ${T}.dmp
1. [NCF-276]/XXI-796914 Columbia server does not serve up proper opendap DDS replies. The Dataset {...} name changes depending on if the request has certain kinds of constraints. Code for a hack was not being used, so restore it. The fix is to effectively ignore differences in Dataset node names if the code is coming from columbia.edu. 2. [NCF-278] The ncgen code is improperly typing int64 integer constants as uint64. 3. [NCF-279] Empty string constants were not being properly filled when their target array is length 1 or more.
2013-11-18 05:26:14 +08:00
xtest::
gcc -c ${CFLAGS} ${T}.c
gcc -o ./vt ${T}.o ${LDFLAGS}
rm -f ctest0.nc junk.cdl
./vt
../ncdump/ncdump ctest0.nc >junk.cdl
# gdb --args ./vt
Reference in New Issue Copy Permalink