gpt4 book ai didi

c - 在 C 中,如何添加第 3 方库并使用 Makefile 从我现有的代码库调用

转载 作者:行者123 更新时间:2023-11-30 16:45:38 25 4
gpt4 key购买 nike

我是物联网和云的新手。

对于物联网项目,我们正在尝试将动态数据发送到云端进行分析。我们在我的目标板中仅使用 c、cpp 代码。 Debian 操作系统。

每隔一秒、2秒、3秒就会有不同类型的数据出现。

在我的目标板中,我想使用第 3 方库(https_client)将数据发送到云端。我需要使用数据访问云中的服务(URL)(仅使用 GET 方法)。

为此,我下载了 https_client 代码并尝试集成到我的代码库中。

下面第一个make文件是原始Makefile,第二个make文件只是第三方软件Makefile,第三个是修改原始Makefile以集成第三方库。

在我的目标板上,我们没有太多空间,那么将数据发送到云端的最佳轻量级方法是什么?我的云仅支持 https 和 WSS。我的做法正确吗?还有其他简单的方法吗?

在修改后的 Makefile 中,我收到以下错误。

make: *** No rule to make target
`https_client-master/https_client-master/main.c', needed by `all'.
Stop.

我对 Makefile 的更改不是标准方式。任何人都可以查看我修改后的 Makefile 并纠正我。

等待您的宝贵建议。

#---------------------------------------------------------------------------
-
--
#1. Below is the original make file of my existing code base
#---------------------------------------------------------------------------
---
SOURCES=./SRC/MMC/Main.cpp \
./SRC/MMC/ModbusMasterController.cpp \
./SRC/DM/DeviceManager.cpp \
.......
./Wrapper/MtrWrapper.cpp


OBJECTS=$(SOURCES:.cpp=.o)
EXECUTABLE=BusMaster
CFLAGS = -c -w -I/usr/include/libxml2 -I./INC/Common -I./INC/ADM -I./INC/MMC
-I./INC/DM -I./INC/CM -I./INC/MMT -I./INC/MPI -I./INC/MMT/DataProc -
I./INC/MMT/CmdProc -I./INC/MMT/CmdProc/Fileoperations -I./INC/SH -
I./INC/FT_MBUS -I./INC/Timer -I./Wrapper -I./INC/DC -Wall

LDFLAGS = -Bdynamic -lSharedMemory -lMessageQueue -luspepc -lxml2 -
lmbusmaster -lrt

CC=g++


all: $(SOURCES) $(EXECUTABLE)

$(EXECUTABLE): $(OBJECTS)
$(CC) $(OBJECTS) -o $@ $(LDFLAGS)

.cpp.o:
$(CC) $(CFLAGS) $< -o $@

clean:
rm -rf $(OBJECTS) $(EXECUTABLE)

#----------------------------------------original make end------------------
-
-------------------

#----------------------------------------2. Below is the 3rd pary Library
Makefile I want to add--------------------------------------
#CROSS = arm-linux-gnueabihf-

MAKE = make

CC = $(CROSS)gcc
LD = $(CROSS)ld
STRIP = $(CROSS)strip

ROOT_DIR = $(CURDIR)
MBEDTLS = $(ROOT_DIR)/mbedtls

CFLAGS = -fPIC -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -O2
LDFLAGS =

INCLUDES = -I$(MBEDTLS)/include
LIBS = $(MBEDTLS)/library/libmbedx509.a $(MBEDTLS)/library/libmbedtls.a
$(MBEDTLS)/library/libmbedcrypto.a

SOURCES = main.c https.c

OBJS = $(SOURCES:.c=.o)

.SUFFIXES:.c .o

all: https_client

mbedtls_make:
@for dir in $(MBEDTLS); do \
$(MAKE) -C $$dir ; \
if [ $$? != 0 ]; then exit 1; fi; \
done

https_client: mbedtls_make $(OBJS)
@echo Linking: $@ ....
$(CC) -o $@ $(OBJS) $(LDFLAGS) $(LIBS)
$(STRIP) -s $@

.c.o:
@echo Compiling: $< ....
$(CC) -c $(CFLAGS) $(INCLUDES) -o $@ $<

clean: mbedtls_clean
rm -f https_client *.o

mbedtls_clean:
@for dir in $(MBEDTLS); do \
$(MAKE) -C $$dir clean; \
if [ $$? != 0 ]; then exit 1; fi; \
done
#----------------------------------------3rd pary Library Makefile end------
-
-------------------------------

#----------------------------------------3. Modified original Makefile to
add
3rd party library----------------

SOURCES=./SRC/MMC/Main.cpp \
./SRC/MMC/ModbusMasterController.cpp \
./SRC/DM/DeviceManager.cpp \
.......
./Wrapper/MtrWrapper.cpp

SOURCES2=./https_client-master/https_client-master/main.c \
./https_client-master/https_client-master/https.c

OBJECTS=$(SOURCES1:.cpp=.o)
OBJS=$(SOURCES2:.c=.o)
.SUFFIXES:.c .o
ROOT_DIR = $(CURDIR)
MBEDTLS = $(ROOT_DIR)/https_client-master/https_client-master/mbedtls
EXECUTABLE1=BusMaster
EXECUTABLE2=https_client
CFLAGS = -c -w -I/usr/include/libxml2 -I./INC/Common -I./INC/ADM -I./INC/MMC
-I./INC/DM -I./INC/CM -I./INC/MMT -I./INC/MPI -I./INC/MMT/DataProc -
I./INC/MMT/CmdProc -I./INC/MMT/CmdProc/Fileoperations -I./INC/SH -
I./INC/FT_MBUS -I./INC/Timer -I./Wrapper -I./INC/DC -Wall
CFLAGS2 = -fPIC -DHAVE_CONFIG_H -D_U_="__attribute__((unused))" -O2
INCLUDES = -I$(MBEDTLS)/include
LIBS = $(MBEDTLS)/library/libmbedx509.a $(MBEDTLS)/library/libmbedtls.a
$(MBEDTLS)/library/libmbedcrypto.a
LDFLAGS = -Bdynamic -lSharedMemory -lMessageQueue -luspepc -lxml2 -
lmbusmaster -lrt
LDFLAGS2 =
STRIP = strip

CC1=g++
CC2=gcc



all: $(SOURCES1) $(EXECUTABLE1) $(SOURCES2) $(EXECUTABLE2)
#$(SOURCES2)
$(EXECUTABLE1): $(OBJECTS)
@echo EXECUTABLE1:
$(CC1) $(OBJECTS) -o $@ $(LDFLAGS)

mbedtls_make:
@echo mbedtls_make: ....
@for dir in $(MBEDTLS); do \
$(MAKE) -C $$dir ; \
if [ $$? != 0 ]; then exit 1; fi; \
done

$(EXECUTABLE2): mbedtls_make $(OBJS)
@echo Linking: $@ ....
$(CC1) -o $@ $(OBJS) $(LDFLAGS2) $(LIBS)
$(STRIP) -s $@

.c.o:
@echo Compiling c: $< ....
$(CC2) -c $(CFLAGS2) $(INCLUDES) -o $@ $<

.cpp.o:
@echo Compiling cpp: $< ....
$(CC1) $(CFLAGS) $< -o $@

clean: mbedtls_clean
rm -rf $(OBJECTS) $(EXECUTABLE1)
rm -f https_client *.o
mbedtls_clean:
@for dir in $(MBEDTLS); do \
$(MAKE) -C $$dir clean; \
if [ $$? != 0 ]; then exit 1; fi; \
done


#------------------------------------------Modified original Makefile end--
-
---------------------------------

最佳答案

我认为你不应该有 2 个来源列表。下面是 MBEDTLS 如何包含在 Makefile 中的片段。

https://github.com/acornblue/AZURE_LAB

#####################################################
# Projects/Multi/Applications/Azure_Sns_DM/Makefile
#####################################################
C_SOURCE = \
...
Middlewares/Third_Parties/mbedtls/library/aes.c \
Middlewares/Third_Parties/mbedtls/library/aesni.c \
...
-DUSE_MBED_TLS \
-DMBEDTLS_CONFIG_FILE='<mbedtls_config.h>'
...
-IMiddlewares/Third_Parties/mbedTLS/include \

关于c - 在 C 中,如何添加第 3 方库并使用 Makefile 从我现有的代码库调用,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/44046104/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com