Now, that i think about it. I somehow remember to have fixed a bug like this some time ago...
What version of codeblocks are you using? Have you tried the latest nightly?
Thank you,
This is a problem left over from the history of "Millennium Bug". The command line buffering of Windows starts from 2048, to 8192, 32768 ... Maybe it is now 65536.
Microsoft's suggestion is to pass the contents of the command line to it in a txt file, if it is indeed the problem.
https://support.microsoft.com/en-us/help/830473/command-prompt-cmd-exe-command-line-string-limitationMy codeblocks is the latest
nightly, and its version number is
'build 12064'. Wondows 10 is 1909, 64bit.
Now there are two problems that need to be solved:
1. Previous command line length limitation.
2. The expected html log file does not appear.
===================
How to reproduce this problem
===================
The Mbed OS is opensource's RTOS.
Note that this Mbed OS is about 1GB, and with the compiled object file, it may exceed 2GB.
1. Need to install python 2, pip, mbed-cli and its dependencies, and gnu gcc for arm.
GNU Tools for Arm Embedded Processors 9-2019q4-major Release
https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm2. Run cmd.exe to command line window, type command:
pip install -U mbed-cli.
3. Go to the folder used for testing, type command:
mbed new test-mbedos, it will download 1GB of content.
4. Go to the test-mbedos folder, it is newly created by the mbed command.
5. Add a main.cpp file:
#include "mbed.h"
DigitalOut led1(LED1);
#define SLEEP_TIME 300 // (msec)
int main()
{
int count = 0;
while (true) {
// Blink LED and wait 0.5 seconds
led1 = !led1;
wait_ms(SLEEP_TIME);
}
}
6. Then continue to enter the order:
mbed export -i codeblocks -m GD32_F450ZI D:\test\test-mbedos>
mbed export -i codeblocks -m GD32_F450ZI [mbed] Working path "D:\test\test-mbedos" (program)
Scan: test-mbedos
D:\test\test-mbedos>
7. If the installation of dependent packages(mbed-cli) fails, you need to delete their version numbers(in mbed-os/requirements.txt).
8. At this time, a CB project file was created (test-mbedos.cbp).
9. Set the path of gcc arm toolchain in CB to start compiling.