- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2164467_en-US
2164467_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2164467_en-US
2164467_en-US
The latest S32DS Platform Tools package (3.6.3) contains MSYS2 environment which is missing features that were included in previous versions:
- pacman package manager
- Windows OS toolchains: UCRT64, MINGW64, MINGW32, CLANG64
Are these intentional omissions or will they be restored in a future release?
The pacman package manager is very useful as it allows users to extend the features of the base MSYS2 environment. Please consider including this.
The Windows toolchains are not important, however we did receive a query from customer about why they were removed, so if there is an explanation we could relay then it would be helpful. For now I advised customer that S32DS is intended for embedded software development targeting NXP products and that the Windows toolchains are not relevant.
I have attached the HTML export from S32DS Extensions and Updates menu.
Thanks,
Gary
Thank you for the swift response Valentin. It is pretty much as I expected and I agree with the decision, was just looking for confirmation that it was indeed deliberate. I notice that the size of MSYS2 has been reduced by > 1 GB which is a significant saving.
I did an experiment and replaced the MSYS2 integrated within S32DS with a new installation containing default packages and it did not break S32DS, I am still able to build using GCC for ARM.
I recommended that customer either installs a new MSYS2 separate from S32DS, or if they really want to they can replace the integrated instance.
Hi @GaryRK,
Yes, those features were removed. S32DS is not supposed to provide a working msys2 environment, we just used it to have Make on Windows mainly.
The decision to cut down MSYS2 to just what we wanted from it was made in order to save on size, MSYS2 was proved to be a bottleneck due to size and large number of files.
If your customer wants to also use it for the other uses MSYS provides it can just replace it with their own, as long as it still contains what we already deploy the IDE should not mind.