1、编译好后，make install 出现以下错误。

main@ubuntu:~/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk$ make install
[ 50%] Built target log_c_sdk
[100%] Built target log_c_sdk_static
Install the project...
-- Install configuration: ""
-- Installing: /home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/Release/lib/liblog_c_sdk.so.2.0.0
-- Up-to-date: /home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/Release/lib/liblog_c_sdk.so
-- Installing: /home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/Release/lib/liblog_c_sdk_static.a
CMake Error at cmake_install.cmake:69 (FILE):
file INSTALL cannot find
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/cJSON.h".

make: *** [install] Error 1

2、cmake_install.cmake做了以下修改才可以编译安装：
FILE(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/include/log_c_sdk" TYPE FILE FILES
# "/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/cJSON.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/lz4.h"
#"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/aos_log.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_define.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_util.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_api.h"
# "/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_http_cont.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_builder.h"
#"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/protobuf-c.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_logs.pb-c.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_producer_client.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_producer_common.h"
"/home/main/workspace/Tbox/TBOX_EC20/ql-ol-sdk/ecpark-app/extlib/aliyun-log-c-sdk/src/log_producer_config.h"
)

3、想知道这样修改是否有问题？

cmake 的时候报错
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
CRYPTO_LIBRARY
linked by target "log_producer_sample" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
linked by target "log_post_logs_sample" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
linked by target "log_producer_benchmark" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
linked by target "video_frame_producer_sample" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
SSL_LIBRARY
linked by target "log_producer_sample" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
linked by target "log_post_logs_sample" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
linked by target "log_producer_benchmark" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample
linked by target "video_frame_producer_sample" in directory /home/pi/lite/aliyun-log-c-sdk-lite/sample

-- Configuring incomplete, errors occurred!

有大佬知道如何处理吗？

如题， @shabicheng 大佬，问下，有没有提供rust版本的sls sdk？找了一波没找到，然后参考了android sdk，发现本质上也是通过jni调用c sdk。rust理论上也是可以调用c sdk。我需要使用的平台主要是桌面端，包括win、mac、linux。想问下，如何生成这些平台的.a文件？

建议改下，以支持windows

我们项目中使用了nodejs开源的http-parser,其中定义了“GET、POST、PUT……”等enum，与aos_define.h文件中enum冲突了，导致无法通过编译。
详见：
http_parser.h 165行
aos_define.h 28行

如标题，发现采用官方提供的方法发送存储的上一次运行未发送成功的数据后，正常发送会返回buffer满的错误，追踪源码发现，producer_manager totalBufferSize在log_producer_client_add_raw_log_buffer之后，变成了很大的值，因为发送完成会使totalBufferSize - sent buffer len，但是并未在发送前增加totalBufferSize的值，使得无符号值变负溢出。需要在发送前增加totalBufferSize的值。此问题只针对log_producer_client_add_raw_log_buffer逻辑
log_producer_result log_producer_manager_send_raw_buffer(log_producer_manager * producer_manager, size_t log_bytes, size_t compressed_bytes, const unsigned char * raw_buffer)
{
// pack lz4_log_buf
lz4_log_buf* lz4_buf = (lz4_log_buf*)malloc(sizeof(lz4_log_buf) + compressed_bytes);
lz4_buf->length = compressed_bytes;
lz4_buf->raw_length = log_bytes;
memcpy(lz4_buf->data, raw_buffer, compressed_bytes);
log_producer_send_param * send_param = create_log_producer_send_param(producer_manager->producer_config, producer_manager, lz4_buf, time(NULL));
//fix totalBufferSize error bug, totalBufferSize will sub buf length after send done
producer_manager->totalBufferSize += lz4_buf->length;
return log_producer_send_data(send_param);
}

void add_log_key_value(log_group_builder* bder,char* k,size_t v_len,char* v,size_t k_len)
log_builder.c 85 行
k用的是v_len
v用的是k_len
另外用CMakeList.txt做build有问题，build不通。
还有日志服务说有Go的API，没找到，现在用cgo调的C API，希望提供Go的。

交叉编译进板子，运行提示如下：
put logs failed
[2017-12-25 20:25:37.340] [ERROR] [1024] [/home/work_sdc1/tenda3/F3_XS/F3V3.0_AC6V2.0_SVN6883/cbb/xs_project/lib/aliyun-log-c-sdk-master/src/aos_transport.c:424] transport failure curl code:1 error:Unsupported protocol
-996
HttpIoError
Unsupported protocol

报不支持的协议
curl -V查看了下所支持的协议如下：
/var # ./curl -V
curl 7.57.0 (mips-unknown-linux-gnu) libcurl/7.57.0
Release-Date: 2017-11-29
Protocols: dict file ftp gopher http imap pop3 rtsp smtp telnet tftp
Features: AsynchDNS IPv6 Largefile UnixSockets

请问：需要curl库支持哪种协议？https协议吗

Since CMake use curl-config, apr-1-1config, and apu-1-config, they needs to be available in PATH. If curl, apr and apr-util are installed to user-defined locations, the directories containing them should be added to PATH.

我们的项目希望用到日志服务，可是嵌入式设备资源紧张，系统是ECOS，有解决方案么？

既然自己是SDK，最好自成一体，不要依赖curl，否则大小和依赖并不太好

log_inner_include.h头文件里面定义的宏

#define __in   // 参数输入
#define __out  // 参数输出

和gcc拓展库<ext/pb_ds/assoc_container.hpp>冲突，导致编译不了

原因是：debug模式启动起来的时候会做一次logrotate，如果时间太长，后台刷新进程会crash
crash点：

Thread 1 (Thread 0x7fdb50cfb700 (LWP 21)):
#0 0x00007fdb576eebd0 in pthread_mutex_lock () from /usr/lib64/libpthread.so.0
#1 0x00000000006af0b7 in _try_flush_loggroup (producer_manager=0x9ca4f8)
at aliyun-log-c-sdk/src/log_producer_manager.c:74

你好：
有2个问题想问下：
1、推荐使用master分支还是使用releaese里的代码？
2、android Android.mk的编译方式没有将对应架构的curl的目录传给编译器，会默认使用系统x86架构的头文件么？会有啥影响么？

SDK底层获取时间是用的time(NULL)接口，对于没有时区概念的IOT设备，会将本地的time接口设置成当前CST时间，此时调用SDK会提示时间不对。无奈只得修改了SDK源码了

gcc --version
gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0

编译错误:

In file included from /work/soft/aliyun-log-c-sdk-0.1.2/src/aos_util.h:5,
                 from /work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.h:12,
                 from /work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c:9:
/work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c: In function 'log_create_http_cont':
/work/soft/aliyun-log-c-sdk-0.1.2/src/aos_string.h:16:5: error: macro expands to multiple statements [-Werror=multistatement-macros]
   16 |     (str)->len = (int)strlen(text); (str)->data = (char *) text
      |     ^
/work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c:128:9: note: in expansion of macro 'aos_str_set'
  128 |         aos_str_set(&(_sts_token), stsToken);
      |         ^~~~~~~~~~~
/work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c:127:5: note: some parts of macro expansion are not guarded by this 'if' clause
  127 |     if(stsToken != NULL)
      |     ^~
In file included from /work/soft/aliyun-log-c-sdk-0.1.2/src/aos_util.h:5,
                 from /work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.h:12,
                 from /work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c:9:
/work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c: In function 'log_create_http_cont_with_lz4_data':
/work/soft/aliyun-log-c-sdk-0.1.2/src/aos_string.h:16:5: error: macro expands to multiple statements [-Werror=multistatement-macros]
   16 |     (str)->len = (int)strlen(text); (str)->data = (char *) text
      |     ^
/work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c:197:5: note: in expansion of macro 'aos_str_set'
  197 |     aos_str_set(&(_sts_token), stsToken);
      |     ^~~~~~~~~~~
/work/soft/aliyun-log-c-sdk-0.1.2/src/log_http_cont.c:196:5: note: some parts of macro expansion are not guarded by this 'if' clause
  196 |     if(stsToken != NULL)
      |     ^~

只是将log_producer_sample.c封装为类，去掉main。其他什么也不修改，jni调用。

#include "aliyun/log_api.h"
#include "aliyun/log_producer_config.h"
#include "aliyun/log_producer_client.h"

生成jni接口报如下错误：

D:/Android/android-ndk-r16b/build//../sources/cxx-stl/gnu-libstdc++/4.9/include\thread:235:15: error: expected
      expression
        return __out << "thread::id of a non-executing thread";
                     `^`
D:/Android/android-ndk-r16b/build//../sources/cxx-stl/gnu-libstdc++/4.9/include\thread:237:15: error: expected
      expression
        return __out << __id._M_thread;
                     ^

源代码直接生成.a和.so没有问题。
mk文件内容如下：

LOCAL_PATH := $(call my-dir)/../aliyun
DEPS_LIB_PATH := $(call my-dir)/../../../../deps

include $(CLEAR_VARS)

LOCAL_MODULE := aliyun

LOCAL_MODULE_FILENAME := libaliyun


LOCAL_SRC_FILES := \
	hmac-sha.c \
	inner_log.c \
	log_api.c \
	log_builder.c \
	log_producer_client.c \
	log_producer_common.c \
	log_producer_config.c \
	log_producer_manager.c \
	log_producer_sender.c \
	log_queue.c \
	log_util.c \
	lz4.c \
	md5.c \
	sds.c \
	sha1.c 

LOCAL_C_INCLUDES := $(LOCAL_PATH)

LOCAL_EXPORT_C_INCLUDES := $(LOCAL_PATH)

LOCAL_EXPORT_LDLIBS := -llog -landroid

LOCAL_CPPFLAGS += -frtti -fexceptions -std=c++14 
LOCAL_CFLAGS += -ffunction-sections -fdata-sections
LOCAL_LDFLAGS += -Wl,--gc-sections 

LOCAL_STATIC_LIBRARIES += curl_static
LOCAL_STATIC_LIBRARIES += ssl_static
LOCAL_STATIC_LIBRARIES += zlib_static

# 编译生成动态库.so
# include $(BUILD_SHARED_LIBRARY) 

# 编译生产静态库.a
include $(BUILD_STATIC_LIBRARY)

$(call import-add-path,$(DEPS_LIB_PATH))
$(call import-module,curl\android)
$(call import-module,openssl\android)
$(call import-module,zlib\android)

Application如下：

APP_PLATFORM := android-19
APP_OPTIM := release
APP_CFLAGS += -Wall
APP_STL := gnustl_static
APP_ABI := armeabi armeabi-v7a x86 arm64-v8a

APP_CPPFLAGS := -frtti -std=c++14 -fsigned-char
APP_LDFLAGS := -latomic

当数据未发送完成producer就destroyed时，上报如下错误
result : 10, log bytes : 3675821, compressed bytes : 3685827, request id : , error message : producer is being destroyed, producer has no time to send this buffer out

除了“程序可靠退出方案”方案外，是否有其他函数或变量来检测数据是否发送完成？

因为log_producer_client_add_log()后执行destroy_log_producer()前时间无法预估，发送的数据大小无法预估，当数据量大时设置的时间总会超时。

log_inner_include.h头文件中存在宏定义#define __in #define __out可能导致编译报错

C Producer Lite中依赖的libcurl需要哪些功能支持， ./configure 要最小支持哪些功能选项？

transport failure curl code:45 error:Failed binding local connection end
-996
HttpIoError
Failed binding local connection end

比如天猫精灵, 这个配置文件里的各种密钥, 是怎么管理的, 明文放在一个配置文件里么?

Hi, I'm SLS's user, I want to build my program with SLS C SDK, but a stable release, not code from master branch.

Centos7.2系统，lite分支的库上传日志报错

报错信息：error message: {"errorCode":"RequestTimeExpired","errorMessage":"request timeThu, 15 Oct 2020 00:00:00 GMT has been expired while server time is Thu, 15 Oct 2020 15:13:44 GMT"}

单线程while(true)处理日志发送的情况下，能够提供一个清理已发送数据的接口，来避免频繁的malloc以及free

README.md

详细配置

| destroy_flusher_wait_sec | flusher线程销毁最大等待时间 | 整数，单位秒，默认为1 |
| destroy_sender_wait_sec | sender线程池销毁最大等待时间 | 整数，单位秒，默认为1 |

#############################
destroy_log_producer_manager函数使用了destroyFlusherWaitTimeoutSec
destroy_log_producer_sender函数也使用了destroyFlusherWaitTimeoutSec，
本意是使用destroySenderWaitTimeoutSec 吧？

void destroy_log_producer_sender(log_producer_sender * producer_sender, log_producer_config * producer_config)
{
if (producer_sender->thread_pool == NULL)
{
return;
}
// add a thread to flush all data out
apr_thread_pool_thread_max_set(producer_sender->thread_pool, producer_config->sendThreadCount + 1);
int32_t flush_count = producer_config->destroyFlusherWaitTimeoutSec > 0 ? producer_config->destroyFlusherWaitTimeoutSec * 100 : MAX_SENDER_FLUSH_COUNT;
int waitCount = 0;

...........

}

我通过后台脚本编译代码来生成给android用的静态库，我搜索了下cmake的跨平台，大多数都是依赖于ide和gradle的，如何直接使用ndk来完成编译呢？

1

看了下代码，VS应该是编译不过的。而且好像windows的部分不完整。有人在windows上使用过吗

live分支windows版本调用destroy_log_producer后WaitforSingleObject一直阻塞，调试后发现flush thread已经return，不明白为啥waitforsingleobject没有返回

c语言实现的命名比较“普通”导致了引入多个类库时候，和其他类库的函数名重复；编译可以通过，但是实际运行时跑去执行了别的类库中实现，导致segment fault

一个堆栈如下图所示，从hmac_sha1()开始跑到别的类库下实现中了。
希望可以改善，较少这种情况

当前我们尝试使用 CMake + MSVC 进行编译，过程中出现各种问题。

aliyun-log-c-sdk live 分支，mac os，make install执行报错

[ 41%] Built target log_c_sdk
[ 82%] Built target log_c_sdk_static
[ 87%] Built target log_producer_benchmark
[ 94%] Built target log_post_logs_sample
[100%] Built target log_producer_sample
Install the project...
-- Install configuration: ""
-- Up-to-date: /usr/local/lib/liblog_c_sdk.2.0.0.dylib
-- Up-to-date: /usr/local/lib/liblog_c_sdk.dylib
-- Installing: /usr/local/lib/liblog_c_sdk_static.a
CMake Error at cmake_install.cmake:69 (file):
file INSTALL cannot find
"/Users/xxxxx/Github/sls/aliyun-log-c-sdk/src/cJSON.h": No such file
or directory.

make: *** [install] Error 1

我在mac上编译，cmake可以执行成功，
make时，会出现这样的错误，可以帮忙分析是什么原因吗，不能在mac上编译吗
Scanning dependencies of target log_c_sdk
[ 2%] Building C object CMakeFiles/log_c_sdk.dir/src/hmac-sha.o
[ 4%] Building C object CMakeFiles/log_c_sdk.dir/src/inner_log.o
[ 7%] Building C object CMakeFiles/log_c_sdk.dir/src/log_api.o
[ 9%] Building C object CMakeFiles/log_c_sdk.dir/src/log_builder.o
[ 12%] Building C object CMakeFiles/log_c_sdk.dir/src/log_producer_client.o
[ 14%] Building C object CMakeFiles/log_c_sdk.dir/src/log_producer_common.o
[ 17%] Building C object CMakeFiles/log_c_sdk.dir/src/log_producer_config.o
[ 19%] Building C object CMakeFiles/log_c_sdk.dir/src/log_producer_manager.o
[ 21%] Building C object CMakeFiles/log_c_sdk.dir/src/log_producer_sender.o
[ 24%] Building C object CMakeFiles/log_c_sdk.dir/src/log_queue.o
[ 26%] Building C object CMakeFiles/log_c_sdk.dir/src/log_util.o
[ 29%] Building C object CMakeFiles/log_c_sdk.dir/src/lz4.o
[ 31%] Building C object CMakeFiles/log_c_sdk.dir/src/md5.o
[ 34%] Building C object CMakeFiles/log_c_sdk.dir/src/sds.o
[ 36%] Building C object CMakeFiles/log_c_sdk.dir/src/sha1.o
[ 39%] Linking C shared library build/Release/lib/liblog_c_sdk.dylib
Undefined symbols for architecture x86_64:
"_curl_easy_cleanup", referenced from:
_post_logs_from_lz4buf in log_api.o
"_curl_easy_getinfo", referenced from:
_post_logs_from_lz4buf in log_api.o
"_curl_easy_init", referenced from:
_post_logs_from_lz4buf in log_api.o
"_curl_easy_perform", referenced from:
_post_logs_from_lz4buf in log_api.o
"_curl_easy_setopt", referenced from:
_post_logs_from_lz4buf in log_api.o
"_curl_easy_strerror", referenced from:
_sls_log_init in log_api.o
_post_logs_from_lz4buf in log_api.o
"_curl_global_cleanup", referenced from:
_sls_log_destroy in log_api.o
"_curl_global_init", referenced from:
_sls_log_init in log_api.o
"_curl_slist_append", referenced from:
_post_logs_from_lz4buf in log_api.o
"_curl_slist_free_all", referenced from:
_post_logs_from_lz4buf in log_api.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [build/Release/lib/liblog_c_sdk.2.0.0.dylib] Error 1
make[1]: *** [CMakeFiles/log_c_sdk.dir/all] Error 2
make: *** [all] Error 2

remove the CMakeList.txt in SAMPLE folder, then you have no need to build the sample code. then this issue gone.

使用live分支，vs2017编译测试代码，上传中文内容后台显示乱码。这个是什么原因呢？

cmake 附加了-DCURL_INCLUDE_DIR目录，make时，还是报
"
aliyun-log-c-sdk-master/src/log_api.c:3:10: fatal error: curl/curl.h: No such file or directory
#include <curl/curl.h>
"

the function void aos_print_log_android(int level, char *log); was just declared, but not defined ?!

When I built the branch persistent, the linker failed with error 'undefined symbol aos_print_log_android'

lite分支下，cmake正常输出产物后，make命令下，会出现不能正常链接到动态库的问题
cannot link directly with dylib/framework, your binary is not an allowed client of /usr/lib/libcrypto.dylib for architecture x86_64