sergiotarxz/nuttx-apps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
e7156be066
nuttx-apps/netutils/libcurl4nx/Kconfig

50 lines
1.0 KiB
Plaintext
Raw Normal View History

apps/netutils/libcurl4nx: This is an initial comit libcurl4nx. It is not complete yet, but I still wish to commit the unfinished bits to describe the roadmap, and because it is already usable. It will be updated and fixed in the future weeks and months, certainly including POST support and later, SSL. Some improvements could be made by anyone. For example, I know the main routine in perform() shall be split into several parts for readability. I apologize in advance for this kind of spaghetti code, but I was short on time to refactor it. Also chunked HTTP transfer encoding would be a nice contribution from anyone interested. It is detected but not yet supported.
2019-05-03 15:26:13 +02:00
#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#
config NETUTILS_LIBCURL4NX
Application.mk and main.c files: Change builtin's entry point from main to xxx_main by macro expansion. This change make the entry point fully compliant with POSIX/ANSI standard.
2019-10-06 14:14:39 +02:00
bool "cURL4nx HTTP client library"
apps/netutils/libcurl4nx: This is an initial comit libcurl4nx. It is not complete yet, but I still wish to commit the unfinished bits to describe the roadmap, and because it is already usable. It will be updated and fixed in the future weeks and months, certainly including POST support and later, SSL. Some improvements could be made by anyone. For example, I know the main routine in perform() shall be split into several parts for readability. I apologize in advance for this kind of spaghetti code, but I was short on time to refactor it. Also chunked HTTP transfer encoding would be a nice contribution from anyone interested. It is detected but not yet supported.
2019-05-03 15:26:13 +02:00
default n
depends on NET_TCP
select LIBC_NETDB
apps/; Change space to tab and help to ---help--- in Kconfig files.
2019-10-06 05:37:19 +02:00
select NETUTILS_NETLIB_GENERICURLPARSER
apps/netutils/libcurl4nx: This is an initial comit libcurl4nx. It is not complete yet, but I still wish to commit the unfinished bits to describe the roadmap, and because it is already usable. It will be updated and fixed in the future weeks and months, certainly including POST support and later, SSL. Some improvements could be made by anyone. For example, I know the main routine in perform() shall be split into several parts for readability. I apologize in advance for this kind of spaghetti code, but I was short on time to refactor it. Also chunked HTTP transfer encoding would be a nice contribution from anyone interested. It is detected but not yet supported.
2019-05-03 15:26:13 +02:00
---help---
Enable the NuttX cURL like library.
if NETUTILS_LIBCURL4NX
config LIBCURL4NX_MAXHOST
int "Maximum URL host length"
default 128
config LIBCURL4NX_MAXPATH
int "Maximum URL path length"
default 128
config LIBCURL4NX_MAXMETHOD
int "Maximum HTTP method length"
default 16
config LIBCURL4NX_MAXUSERAGENT
int "Maximum HTTP user agent length"
default 64
config LIBCURL4NX_MAXHEADERLINE
int "Maximum receivable header line"
default 128
config LIBCURL4NX_RXBUFLEN
int "Initial RX buffer size"
default 512
config LIBCURL4NX_MINRXBUFLEN
int "Minimum RX buffer size for CURL4NXOPT_BUFFERSIZE"
default 16
config LIBCURL4NX_MAXRXBUFLEN
int "Maximum RX buffer size for CURL4NXOPT_BUFFERSIZE"
Change the defaults of stack size configs to DEFAULT_TASK_STACKSIZE This commit changes only ones with the default 2048 and leaves the others. E.g. this leaves SYSTEM_RAMTEST_STACKSIZE, whose default is 1024. I guess those need to be inspected one-by-one.
2020-03-27 06:10:33 +01:00
default DEFAULT_TASK_STACKSIZE
apps/netutils/libcurl4nx: This is an initial comit libcurl4nx. It is not complete yet, but I still wish to commit the unfinished bits to describe the roadmap, and because it is already usable. It will be updated and fixed in the future weeks and months, certainly including POST support and later, SSL. Some improvements could be made by anyone. For example, I know the main routine in perform() shall be split into several parts for readability. I apologize in advance for this kind of spaghetti code, but I was short on time to refactor it. Also chunked HTTP transfer encoding would be a nice contribution from anyone interested. It is detected but not yet supported.
2019-05-03 15:26:13 +02:00
endif
Reference in New Issue Copy Permalink