From 21750ea8971fb40ef24cf7277659ec89cf4fb1bf Mon Sep 17 00:00:00 2001 From: scuri Date: Wed, 24 Jun 2009 20:58:10 +0000 Subject: *** empty log message *** --- html/en/capture_guide.html | 3 ++- html/en/proc_guide.html | 3 ++- include/im_format_avi.h | 3 ++- include/im_format_jp2.h | 3 ++- include/im_format_wmv.h | 3 ++- include/im_process.h | 3 ++- 6 files changed, 12 insertions(+), 6 deletions(-) diff --git a/html/en/capture_guide.html b/html/en/capture_guide.html index b3f84c3..c610784 100644 --- a/html/en/capture_guide.html +++ b/html/en/capture_guide.html @@ -61,7 +61,8 @@ imVideoCaptureDestroy(vc);

Building

You should include the <im_capture.h> header and link with the - "im_capture.lib" library. This library is independent of all IM libraries.

+ "im_capture.lib" library. This library is independent of all IM libraries.  + In Lua call require"imlua_capture".

To link with the capture library in Windows using Visual C you will need the file "strmiids.lib". To link it using Dev-C++ or Mingw 3 you will need the "im_capture.dll".

diff --git a/html/en/proc_guide.html b/html/en/proc_guide.html index 5226702..f542cc3 100644 --- a/html/en/proc_guide.html +++ b/html/en/proc_guide.html @@ -15,7 +15,8 @@

You should include one or more headers: <im_process_ana.h>, <im_process_glo.h>, <im_process_loc.h> and <im_process_pon.h>. And you must - link with the "im_process.a/im_process.lib" library.

+ link with the "im_process.a/im_process.lib" library. In Lua call + require"imlua_process".

The processing operations are very simple to use. Usually you just have to call the respective function. But you will have to ensure yourself that the image parameters for the input and output data are correct. Here is an diff --git a/include/im_format_avi.h b/include/im_format_avi.h index 32eb7fa..ae9fe99 100644 --- a/include/im_format_avi.h +++ b/include/im_format_avi.h @@ -21,7 +21,8 @@ extern "C" { * When writing a new file you must use an ".avi" extension, or the Windows API will fail. \n * You must link the application with "im_avi.lib" * and you must call the function \ref imFormatRegisterAVI once - * to register the format into the IM core library. \n + * to register the format into the IM core library. + * In Lua call require"imlua_avi". \n * Depends also on the VFW library (vfw32.lib). * When using the "im_avi.dll" this extra library is not necessary. \n * If using Cygwin or MingW must link with "-lvfw32". diff --git a/include/im_format_jp2.h b/include/im_format_jp2.h index 96c1c0a..5a8cd73 100644 --- a/include/im_format_jp2.h +++ b/include/im_format_jp2.h @@ -21,7 +21,8 @@ extern "C" { * \par * You must link the application with "im_jp2.lib" * and you must call the function \ref imFormatRegisterJP2 once - * to register the format into the IM core library. \n + * to register the format into the IM core library. + * In Lua call require"imlua_jp2". \n * \par * Access to the JPEG2000 file format uses libJasper version 1.900.1 \n * http://www.ece.uvic.ca/~mdadams/jasper \n diff --git a/include/im_format_wmv.h b/include/im_format_wmv.h index 10007b8..b60d4c4 100644 --- a/include/im_format_wmv.h +++ b/include/im_format_wmv.h @@ -21,7 +21,8 @@ extern "C" { * Access to the WMV format uses Windows Media SDK. Available in Windows Only. \n * You must link the application with "im_wmv.lib" * and you must call the function \ref imFormatRegisterWMV once - * to register the format into the IM core library. \n + * to register the format into the IM core library. + * In Lua call require"imlua_wmv". \n * Depends also on the WMF SDK (wmvcore.lib). * When using the "im_wmv.dll" this extra library is not necessary. * \par diff --git a/include/im_process.h b/include/im_process.h index e0d3d6c..812dad1 100644 --- a/include/im_process.h +++ b/include/im_process.h @@ -21,7 +21,8 @@ extern "C" { * \par * Several image processing functions based on the \ref imImage structure. * \par - * You must link the application with "im_process.lib/.a/.so". \n + * You must link the application with "im_process.lib/.a/.so". + * In Lua call require"imlua_process". \n * Some complex operations use the \ref counter.\n * There is no check on the input/output image properties, * check each function documentation before using it. -- cgit v1.2.3