12/12/2023 0 Comments Download git 2.9.0![]() ![]() The zip file approach makes it difficult for a distributed engineering team: I have to distribute the SDK zip files and make sure it is built the same: having it pulled from a VCS makes things a lot easier. It is doable, but painful: I rather would pull all the files from a repository and I’m done. Build Integration: the zip file approach means that I have to integrate the SDK myself into my CI build system or build server.I want to have an SDK which makes it easy for me to switch between versions with just providing a Tag for a checkout. Upgrade: You are on version 2.8.0, now 2.9.0 comes out with a new zip file: what are the changes? You have to compare the content of the files, making it really hard (or even impossible) to upgrade a project to a newer SDK version, especially if I had to do patches or changes to the previous SDK.I want to have an SDK which includes all the devices I need, not multiple single device SDK. Using multiple devices means having many SDK zip files, each around 50-120 MByte in size, and the zip files are maybe 90% the same, with just some device specific information being different. ![]() ![]() Per Device: It requires a separate SDK package/zip file for every device.For a more common development flow it is not good: That SDK concept is OK for a single project or device. The current SDK package concept so far used by NXP is basically a zip file which can be configured and downloaded from or directly from the Eclipse based MCUXpresso IDE. The SDK is a set of device drivers (UART, SPI, USB, …), middle-ware (GUI library, RTOS, utilities, …), example projects, documentation and information for flash programming and debuggers. NXP provides the SDK (at least the part of it which is NXP IP) with a very permissible BSD-3 license or see this license file on GitHub. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |