2018-12-07 05:56:42 +08:00
|
|
|
# Copyright 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
|
|
|
|
|
# 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014,
|
|
|
|
|
# 2015, 2016, 2017, 2018
|
|
|
|
|
# University Corporation for Atmospheric Research/Unidata.
|
|
|
|
|
|
|
|
|
|
# See netcdf-c/COPYRIGHT file for more info.
|
|
|
|
|
|
2017-03-09 08:01:10 +08:00
|
|
|
message(STATUS "CMAKE_SOURCE_DIR=${CMAKE_SOURCE_DIR}")
|
|
|
|
|
message(STATUS "CMAKE_BINARY_DIR=${CMAKE_BINARY_DIR}")
|
|
|
|
|
message(STATUS "CMAKE_CURRENT_SOURCE_DIR=${CMAKE_CURRENT_SOURCE_DIR}")
|
|
|
|
|
message(STATUS "CMAKE_CURRENT_BINARY_DIR=${CMAKE_CURRENT_BINARY_DIR}")
|
|
|
|
|
|
|
|
|
|
add_definitions(-D"TOPSRCDIR=${CMAKE_SOURCE_DIR}")
|
|
|
|
|
add_definitions(-D"TOPBINDIR=${CMAKE_BINARY_DIR}")
|
|
|
|
|
|
2014-09-12 05:44:56 +08:00
|
|
|
INCLUDE_DIRECTORIES(${CMAKE_BINARY_DIR}/include)
|
|
|
|
|
|
2014-08-23 23:34:16 +08:00
|
|
|
SET (nc_test_SRC
|
|
|
|
|
nc_test.c
|
|
|
|
|
error.c
|
|
|
|
|
util.c
|
|
|
|
|
)
|
2015-12-23 03:02:18 +08:00
|
|
|
|
2020-08-12 05:46:18 +08:00
|
|
|
|
|
|
|
|
SET (nc_test_m4_SOURCES test_get test_put test_read test_write)
|
|
|
|
|
FOREACH (F ${nc_test_m4_SOURCES})
|
|
|
|
|
GEN_m4(${F} dest)
|
|
|
|
|
LIST(APPEND nc_test_SRC ${dest})
|
|
|
|
|
ENDFOREACH()
|
|
|
|
|
|
2012-08-07 04:53:34 +08:00
|
|
|
ADD_EXECUTABLE(nc_test ${nc_test_SRC})
|
2020-08-12 05:46:18 +08:00
|
|
|
TARGET_INCLUDE_DIRECTORIES(nc_test PRIVATE ${CMAKE_CURRENT_SOURCE_DIR})
|
2014-08-23 23:34:16 +08:00
|
|
|
TARGET_LINK_LIBRARIES(nc_test
|
|
|
|
|
netcdf
|
|
|
|
|
${HAVE_LIBM}
|
|
|
|
|
)
|
2012-08-07 04:53:34 +08:00
|
|
|
|
2015-07-29 02:24:13 +08:00
|
|
|
# Some extra stand-alone tests
|
Codify cross-platform file paths
The netcdf-c code has to deal with a variety of platforms:
Windows, OSX, Linux, Cygwin, MSYS, etc. These platforms differ
significantly in the kind of file paths that they accept. So in
order to handle this, I have created a set of replacements for
the most common file system operations such as _open_ or _fopen_
or _access_ to manage the file path differences correctly.
A more limited version of this idea was already implemented via
the ncwinpath.h and dwinpath.c code. So this can be viewed as a
replacement for that code. And in path in many cases, the only
change that was required was to replace '#include <ncwinpath.h>'
with '#include <ncpathmgt.h>' and then replace file operation
calls with the NCxxx equivalent from ncpathmgr.h Note that
recently, the ncwinpath.h was renamed ncpathmgmt.h, so this pull
request should not require dealing with winpath.
The heart of the change is include/ncpathmgmt.h, which provides
alternate operations such as NCfopen or NCaccess and which properly
parse and rebuild path arguments to work for the platform on which
the code is executing. This mostly matters for Windows because of the
way that it uses backslash and drive letters, as compared to *nix*.
One important feature is that the user can do string manipulations
on a file path without having to worry too much about the platform
because the path management code will properly handle most mixed cases.
So one can for example concatenate a path suffix that uses forward
slashes to a Windows path and have it work correctly.
The conversion code is in libdispatch/dpathmgr.c, and the
important function there is NCpathcvt which does the proper
conversions to the local path format.
As a rule, most code should just replace their file operations with
the corresponding NCxxx ones defined in include/ncpathmgmt.h. These
NCxxx functions all call NCpathcvt on their path arguments before
executing the actual file operation.
In some rare cases, the client may need to directly use NCpathcvt,
but this should be avoided as much as possible. If there is a need
for supporting a new file operation not already in ncpathmgmt.h, then
use the code in dpathmgr.c as a template. Also please notify Unidata
so we can include it as a formal part or our supported operations.
Also, if you see an operation in the library that is not using the
NCxxx form, then please submit an issue so we can fix it.
Misc. Changes:
* Clean up the utf8 testing code; it is impossible to get some
tests to work under windows using shell scripts; the args do
not pass as utf8 but as some other encoding.
* Added an extra utf8 test case: test_unicode_path.sh
* Add a true test for HDF5 1.10.6 or later because as noted in
PR https://github.com/Unidata/netcdf-c/pull/1794,
HDF5 changed its Windows file path handling.
2021-03-05 04:41:31 +08:00
|
|
|
SET(TESTS t_nc tst_small tst_misc tst_norm tst_names tst_nofill tst_nofill2 tst_nofill3 tst_meta tst_inq_type tst_utf8_phrases tst_global_fillval tst_max_var_dims tst_formats tst_def_var_fill tst_err_enddef tst_default_format)
|
|
|
|
|
|
|
|
|
|
IF(NOT MSVC)
|
|
|
|
|
SET(TESTS ${TESTS} tst_utf8_validate)
|
|
|
|
|
ENDIF()
|
2012-09-15 05:35:25 +08:00
|
|
|
|
2015-01-28 04:57:51 +08:00
|
|
|
IF(NOT HAVE_BASH)
|
2014-04-22 01:15:33 +08:00
|
|
|
SET(TESTS ${TESTS} tst_atts3)
|
2012-09-15 05:35:25 +08:00
|
|
|
ENDIF()
|
2012-08-07 04:53:34 +08:00
|
|
|
|
2013-08-27 03:50:27 +08:00
|
|
|
IF(USE_PNETCDF)
|
2014-04-22 01:15:33 +08:00
|
|
|
build_bin_test_no_prefix(tst_pnetcdf)
|
|
|
|
|
build_bin_test_no_prefix(tst_parallel2)
|
2015-10-30 00:27:31 +08:00
|
|
|
build_bin_test_no_prefix(tst_addvar)
|
2014-04-22 01:15:33 +08:00
|
|
|
add_sh_test(nc_test run_pnetcdf_test)
|
2015-10-30 00:27:31 +08:00
|
|
|
add_bin_test(nc_test tst_formatx_pnetcdf)
|
2018-07-28 15:49:07 +08:00
|
|
|
add_bin_test(nc_test tst_default_format_pnetcdf)
|
2013-08-27 03:50:27 +08:00
|
|
|
ENDIF()
|
|
|
|
|
|
2012-12-06 02:35:42 +08:00
|
|
|
IF(LARGE_FILE_TESTS)
|
2017-08-12 08:18:11 +08:00
|
|
|
SET(TESTS ${TESTS} quick_large_files tst_big_var6 tst_big_var2 tst_big_rvar tst_big_var tst_large tst_large_cdf5)
|
2013-08-29 06:30:41 +08:00
|
|
|
IF(NOT MSVC)
|
|
|
|
|
SET(TESTS ${TESTS} large_files)
|
|
|
|
|
ENDIF()
|
2014-09-12 05:44:56 +08:00
|
|
|
|
2012-12-06 02:35:42 +08:00
|
|
|
ENDIF()
|
|
|
|
|
|
2020-08-18 09:15:47 +08:00
|
|
|
SET(TESTFILES ${TESTFILES} tst_diskless tst_diskless3 tst_diskless4 tst_diskless5 tst_inmemory tst_open_mem)
|
|
|
|
|
IF(USE_HDF5)
|
2018-05-12 05:30:19 +08:00
|
|
|
SET(TESTFILES ${TESTFILES} tst_diskless2)
|
2018-10-12 02:09:42 +08:00
|
|
|
SET(TESTS ${TESTS} tst_diskless6)
|
2012-08-07 07:07:40 +08:00
|
|
|
ENDIF()
|
|
|
|
|
|
2013-02-15 04:24:02 +08:00
|
|
|
# Build executables required for the shell scripts.
|
|
|
|
|
FOREACH(BINFILE ${TESTFILES})
|
2014-04-22 01:15:33 +08:00
|
|
|
build_bin_test(${BINFILE})
|
2013-02-15 04:24:02 +08:00
|
|
|
ENDFOREACH()
|
2012-08-07 07:07:40 +08:00
|
|
|
|
2013-02-15 04:24:02 +08:00
|
|
|
# Process single-file test files.
|
2013-01-16 06:43:09 +08:00
|
|
|
FOREACH(CTEST ${TESTS})
|
2014-04-22 01:15:33 +08:00
|
|
|
add_bin_test(nc_test ${CTEST})
|
2012-08-07 04:53:34 +08:00
|
|
|
ENDFOREACH()
|
|
|
|
|
|
|
|
|
|
ADD_TEST(nc_test ${EXECUTABLE_OUTPUT_PATH}/nc_test)
|
2012-08-07 07:07:40 +08:00
|
|
|
|
2016-09-01 05:48:10 +08:00
|
|
|
IF(BUILD_UTILITIES)
|
|
|
|
|
|
|
|
|
|
add_sh_test(nc_test run_diskless)
|
|
|
|
|
IF(BUILD_MMAP)
|
|
|
|
|
add_sh_test(nc_test run_mmap)
|
2017-12-02 06:23:26 +08:00
|
|
|
SET_TESTS_PROPERTIES(nc_test_run_mmap PROPERTIES RUN_SERIAL TRUE)
|
2016-09-01 05:48:10 +08:00
|
|
|
ENDIF(BUILD_MMAP)
|
2017-05-03 23:58:49 +08:00
|
|
|
add_sh_test(nc_test run_diskless5)
|
2018-02-26 12:45:31 +08:00
|
|
|
add_sh_test(nc_test run_inmemory)
|
2018-11-04 01:51:10 +08:00
|
|
|
IF(LARGE_FILE_TESTS)
|
|
|
|
|
add_sh_test(nc_test run_diskless2)
|
|
|
|
|
ENDIF()
|
2013-02-13 06:22:54 +08:00
|
|
|
|
This PR adds EXPERIMENTAL support for accessing data in the
cloud using a variant of the Zarr protocol and storage
format. This enhancement is generically referred to as "NCZarr".
The data model supported by NCZarr is netcdf-4 minus the user-defined
types and the String type. In this sense it is similar to the CDF-5
data model.
More detailed information about enabling and using NCZarr is
described in the document NUG/nczarr.md and in a
[Unidata Developer's blog entry](https://www.unidata.ucar.edu/blogs/developer/en/entry/overview-of-zarr-support-in).
WARNING: this code has had limited testing, so do use this version
for production work. Also, performance improvements are ongoing.
Note especially the following platform matrix of successful tests:
Platform | Build System | S3 support
------------------------------------
Linux+gcc | Automake | yes
Linux+gcc | CMake | yes
Visual Studio | CMake | no
Additionally, and as a consequence of the addition of NCZarr,
major changes have been made to the Filter API. NOTE: NCZarr
does not yet support filters, but these changes are enablers for
that support in the future. Note that it is possible
(probable?) that there will be some accidental reversions if the
changes here did not correctly mimic the existing filter testing.
In any case, previously filter ids and parameters were of type
unsigned int. In order to support the more general zarr filter
model, this was all converted to char*. The old HDF5-specific,
unsigned int operations are still supported but they are
wrappers around the new, char* based nc_filterx_XXX functions.
This entailed at least the following changes:
1. Added the files libdispatch/dfilterx.c and include/ncfilter.h
2. Some filterx utilities have been moved to libdispatch/daux.c
3. A new entry, "filter_actions" was added to the NCDispatch table
and the version bumped.
4. An overly complex set of structs was created to support funnelling
all of the filterx operations thru a single dispatch
"filter_actions" entry.
5. Move common code to from libhdf5 to libsrc4 so that it is accessible
to nczarr.
Changes directly related to Zarr:
1. Modified CMakeList.txt and configure.ac to support both C and C++
-- this is in support of S3 support via the awd-sdk libraries.
2. Define a size64_t type to support nczarr.
3. More reworking of libdispatch/dinfermodel.c to
support zarr and to regularize the structure of the fragments
section of a URL.
Changes not directly related to Zarr:
1. Make client-side filter registration be conditional, with default off.
2. Hack include/nc4internal.h to make some flags added by Ed be unique:
e.g. NC_CREAT, NC_INDEF, etc.
3. cleanup include/nchttp.h and libdispatch/dhttp.c.
4. Misc. changes to support compiling under Visual Studio including:
* Better testing under windows for dirent.h and opendir and closedir.
5. Misc. changes to the oc2 code to support various libcurl CURLOPT flags
and to centralize error reporting.
6. By default, suppress the vlen tests that have unfixed memory leaks; add option to enable them.
7. Make part of the nc_test/test_byterange.sh test be contingent on remotetest.unidata.ucar.edu being accessible.
Changes Left TO-DO:
1. fix provenance code, it is too HDF5 specific.
2020-06-29 08:02:47 +08:00
|
|
|
IF(ENABLE_BYTERANGE)
|
2020-01-08 08:40:03 +08:00
|
|
|
build_bin_test_no_prefix(tst_byterange)
|
|
|
|
|
add_sh_test(nc_test test_byterange)
|
This PR adds EXPERIMENTAL support for accessing data in the
cloud using a variant of the Zarr protocol and storage
format. This enhancement is generically referred to as "NCZarr".
The data model supported by NCZarr is netcdf-4 minus the user-defined
types and the String type. In this sense it is similar to the CDF-5
data model.
More detailed information about enabling and using NCZarr is
described in the document NUG/nczarr.md and in a
[Unidata Developer's blog entry](https://www.unidata.ucar.edu/blogs/developer/en/entry/overview-of-zarr-support-in).
WARNING: this code has had limited testing, so do use this version
for production work. Also, performance improvements are ongoing.
Note especially the following platform matrix of successful tests:
Platform | Build System | S3 support
------------------------------------
Linux+gcc | Automake | yes
Linux+gcc | CMake | yes
Visual Studio | CMake | no
Additionally, and as a consequence of the addition of NCZarr,
major changes have been made to the Filter API. NOTE: NCZarr
does not yet support filters, but these changes are enablers for
that support in the future. Note that it is possible
(probable?) that there will be some accidental reversions if the
changes here did not correctly mimic the existing filter testing.
In any case, previously filter ids and parameters were of type
unsigned int. In order to support the more general zarr filter
model, this was all converted to char*. The old HDF5-specific,
unsigned int operations are still supported but they are
wrappers around the new, char* based nc_filterx_XXX functions.
This entailed at least the following changes:
1. Added the files libdispatch/dfilterx.c and include/ncfilter.h
2. Some filterx utilities have been moved to libdispatch/daux.c
3. A new entry, "filter_actions" was added to the NCDispatch table
and the version bumped.
4. An overly complex set of structs was created to support funnelling
all of the filterx operations thru a single dispatch
"filter_actions" entry.
5. Move common code to from libhdf5 to libsrc4 so that it is accessible
to nczarr.
Changes directly related to Zarr:
1. Modified CMakeList.txt and configure.ac to support both C and C++
-- this is in support of S3 support via the awd-sdk libraries.
2. Define a size64_t type to support nczarr.
3. More reworking of libdispatch/dinfermodel.c to
support zarr and to regularize the structure of the fragments
section of a URL.
Changes not directly related to Zarr:
1. Make client-side filter registration be conditional, with default off.
2. Hack include/nc4internal.h to make some flags added by Ed be unique:
e.g. NC_CREAT, NC_INDEF, etc.
3. cleanup include/nchttp.h and libdispatch/dhttp.c.
4. Misc. changes to support compiling under Visual Studio including:
* Better testing under windows for dirent.h and opendir and closedir.
5. Misc. changes to the oc2 code to support various libcurl CURLOPT flags
and to centralize error reporting.
6. By default, suppress the vlen tests that have unfixed memory leaks; add option to enable them.
7. Make part of the nc_test/test_byterange.sh test be contingent on remotetest.unidata.ucar.edu being accessible.
Changes Left TO-DO:
1. fix provenance code, it is too HDF5 specific.
2020-06-29 08:02:47 +08:00
|
|
|
ENDIF()
|
2019-04-20 10:32:26 +08:00
|
|
|
|
|
|
|
|
IF(BUILD_MMAP)
|
|
|
|
|
add_sh_test(nc_test run_mmap)
|
|
|
|
|
ENDIF()
|
|
|
|
|
|
|
|
|
|
ENDIF(BUILD_UTILITIES)
|
Provide byte-range reading of remote datasets
re: issue https://github.com/Unidata/netcdf-c/issues/1251
Assume that you have the URL to a remote dataset
which is a normal netcdf-3 or netcdf-4 file.
This PR allows the netcdf-c to read that dataset's
contents as a netcdf file using HTTP byte ranges
if the remote server supports byte-range access.
Originally, this PR was set up to access Amazon S3 objects,
but it can also access other remote datasets such as those
provided by a Thredds server via the HTTPServer access protocol.
It may also work for other kinds of servers.
Note that this is not intended as a true production
capability because, as is known, this kind of access to
can be quite slow. In addition, the byte-range IO drivers
do not currently do any sort of optimization or caching.
An additional goal here is to gain some experience with
the Amazon S3 REST protocol.
This architecture and its use documented in
the file docs/byterange.dox.
There are currently two test cases:
1. nc_test/tst_s3raw.c - this does a simple open, check format, close cycle
for a remote netcdf-3 file and a remote netcdf-4 file.
2. nc_test/test_s3raw.sh - this uses ncdump to investigate some remote
datasets.
This PR also incorporates significantly changed model inference code
(see the superceded PR https://github.com/Unidata/netcdf-c/pull/1259).
1. It centralizes the code that infers the dispatcher.
2. It adds support for byte-range URLs
Other changes:
1. NC_HDF5_finalize was not being properly called by nc_finalize().
2. Fix minor bug in ncgen3.l
3. fix memory leak in nc4info.c
4. add code to walk the .daprc triples and to replace protocol=
fragment tag with a more general mode= tag.
Final Note:
Th inference code is still way too complicated. We need to move
to the validfile() model used by netcdf Java, where each
dispatcher is asked if it can process the file. This decentralizes
the inference code. This will be done after all the major new
dispatchers (PIO, Zarr, etc) have been implemented.
2019-01-02 09:27:36 +08:00
|
|
|
|
2013-02-15 04:24:02 +08:00
|
|
|
# Copy some test files from current source dir to out-of-tree build dir.
|
|
|
|
|
FILE(GLOB COPY_FILES ${CMAKE_CURRENT_SOURCE_DIR}/*.nc ${CMAKE_CURRENT_SOURCE_DIR}/*.sh)
|
|
|
|
|
FILE(COPY ${COPY_FILES} DESTINATION ${CMAKE_CURRENT_BINARY_DIR}/)
|
2013-10-17 06:44:11 +08:00
|
|
|
IF(MSVC)
|
Provide byte-range reading of remote datasets
re: issue https://github.com/Unidata/netcdf-c/issues/1251
Assume that you have the URL to a remote dataset
which is a normal netcdf-3 or netcdf-4 file.
This PR allows the netcdf-c to read that dataset's
contents as a netcdf file using HTTP byte ranges
if the remote server supports byte-range access.
Originally, this PR was set up to access Amazon S3 objects,
but it can also access other remote datasets such as those
provided by a Thredds server via the HTTPServer access protocol.
It may also work for other kinds of servers.
Note that this is not intended as a true production
capability because, as is known, this kind of access to
can be quite slow. In addition, the byte-range IO drivers
do not currently do any sort of optimization or caching.
An additional goal here is to gain some experience with
the Amazon S3 REST protocol.
This architecture and its use documented in
the file docs/byterange.dox.
There are currently two test cases:
1. nc_test/tst_s3raw.c - this does a simple open, check format, close cycle
for a remote netcdf-3 file and a remote netcdf-4 file.
2. nc_test/test_s3raw.sh - this uses ncdump to investigate some remote
datasets.
This PR also incorporates significantly changed model inference code
(see the superceded PR https://github.com/Unidata/netcdf-c/pull/1259).
1. It centralizes the code that infers the dispatcher.
2. It adds support for byte-range URLs
Other changes:
1. NC_HDF5_finalize was not being properly called by nc_finalize().
2. Fix minor bug in ncgen3.l
3. fix memory leak in nc4info.c
4. add code to walk the .daprc triples and to replace protocol=
fragment tag with a more general mode= tag.
Final Note:
Th inference code is still way too complicated. We need to move
to the validfile() model used by netcdf Java, where each
dispatcher is asked if it can process the file. This decentralizes
the inference code. This will be done after all the major new
dispatchers (PIO, Zarr, etc) have been implemented.
2019-01-02 09:27:36 +08:00
|
|
|
#MESSAGE(STATUS "XXX")
|
|
|
|
|
#MESSAGE(STATUS "${COPY_FILES}")
|
|
|
|
|
#MESSAGE(STATUS "${RUNTIME_OUTPUT_DIRECTORY}")
|
2014-04-22 01:15:33 +08:00
|
|
|
FILE(COPY ${COPY_FILES} DESTINATION ${RUNTIME_OUTPUT_DIRECTORY}/)
|
2013-10-17 06:44:11 +08:00
|
|
|
ENDIF()
|
|
|
|
|
|
2013-02-13 06:22:54 +08:00
|
|
|
|
2013-06-04 00:42:04 +08:00
|
|
|
## Specify files to be distributed by 'make dist'
|
|
|
|
|
FILE(GLOB CUR_EXTRA_DIST RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} ${CMAKE_CURRENT_SOURCE_DIR}/*.c ${CMAKE_CURRENT_SOURCE_DIR}/*.h ${CMAKE_CURRENT_SOURCE_DIR}/*.sh)
|
|
|
|
|
SET(CUR_EXTRA_DIST ${CUR_EXTRA_DIST} CMakeLists.txt Makefile.am)
|
Provide byte-range reading of remote datasets
re: issue https://github.com/Unidata/netcdf-c/issues/1251
Assume that you have the URL to a remote dataset
which is a normal netcdf-3 or netcdf-4 file.
This PR allows the netcdf-c to read that dataset's
contents as a netcdf file using HTTP byte ranges
if the remote server supports byte-range access.
Originally, this PR was set up to access Amazon S3 objects,
but it can also access other remote datasets such as those
provided by a Thredds server via the HTTPServer access protocol.
It may also work for other kinds of servers.
Note that this is not intended as a true production
capability because, as is known, this kind of access to
can be quite slow. In addition, the byte-range IO drivers
do not currently do any sort of optimization or caching.
An additional goal here is to gain some experience with
the Amazon S3 REST protocol.
This architecture and its use documented in
the file docs/byterange.dox.
There are currently two test cases:
1. nc_test/tst_s3raw.c - this does a simple open, check format, close cycle
for a remote netcdf-3 file and a remote netcdf-4 file.
2. nc_test/test_s3raw.sh - this uses ncdump to investigate some remote
datasets.
This PR also incorporates significantly changed model inference code
(see the superceded PR https://github.com/Unidata/netcdf-c/pull/1259).
1. It centralizes the code that infers the dispatcher.
2. It adds support for byte-range URLs
Other changes:
1. NC_HDF5_finalize was not being properly called by nc_finalize().
2. Fix minor bug in ncgen3.l
3. fix memory leak in nc4info.c
4. add code to walk the .daprc triples and to replace protocol=
fragment tag with a more general mode= tag.
Final Note:
Th inference code is still way too complicated. We need to move
to the validfile() model used by netcdf Java, where each
dispatcher is asked if it can process the file. This decentralizes
the inference code. This will be done after all the major new
dispatchers (PIO, Zarr, etc) have been implemented.
2019-01-02 09:27:36 +08:00
|
|
|
SET(CUR_EXTRA_DIST ${CUR_EXTRA_DIST} test_get.m4 test_put.m4 test_read.m4 test_write.m4 ref_tst_diskless2.cdl tst_diskless5.cdl
|
2019-04-20 10:32:26 +08:00
|
|
|
ref_tst_diskless3_create.cdl ref_tst_diskless3_open.cdl
|
2020-09-25 04:33:58 +08:00
|
|
|
ref_tst_http_nc3.cdl ref_tst_http_nc4a.cdl ref_tst_http_nc4b.cdl ref_tst_http_nc4c.cdl)
|
2013-08-27 03:50:27 +08:00
|
|
|
ADD_EXTRA_DIST("${CUR_EXTRA_DIST}")
|
