Big news from Microchip: they've released XC8 Compiler v3.10. However, for those of us relying on GCBASIC with PIC-AS, this update brings a major setback. Up until XC8 v3.00, GCBASIC enjoyed full integration with the compiler, making our workflows smooth and efficient. Sadly, v3.10 changes that.
The Issue
Microchip has removed internal device-support files from the compiler. Now, you must specify a Device Family Pack (DFP) using the -mdfp option for every project. This breaks the seamless integration GCBASIC had with PIC-AS up to v3.00, making it significantly harder to compile GCBASIC source code outside of MPLAB X or VS Code.
From Microchip’s release notes:
"The internal device-support files are no longer shipped with the compiler, and whenever you build a project, a DFP must be specified using the option. If you use the MPLAB X IDE or VS Code to build projects, you do not need to take any action, as the IDE will continue to manage DFPs for you. If, however, you build projects on the command line or via build scripts outside of an IDE, you will first need to download the appropriate DFP, unpack it on your build machine, and then specify the path to this DFP using the -mdfp option."
This means extra steps to download DFPs from Microchip’s pack repository and manually configure them. It’s a frustrating disruption, especially for those of us who loved the streamlined process with GCBASIC and XC8 v3.00 or earlier.
Why This Matters
This change feels like a step backward. It’s not clever, not smart, and definitely not collaborative. For the GCBASIC community, it undermines the full integration we’ve relied on, adding unnecessary complexity to our workflows. GCBASIC is all about making microcontroller programming accessible, and this update makes that harder.
What Can We Do?
If you use MPLAB X , you’re in luck—the IDE handle DFPs automatically so I just need to figure out the DFPs automatically. I think we have a tool that will do this but means more work, more maintenance and this will not be ready for many months.
For command-line users, you’ll need to manually download and unpack DFPs, then update your build scripts with the -mdfp path. Check the MPLAB XC8 C Compiler User’s Guide for details.
Raise your voice! Let’s share feedback with Microchip about how this impacts our community. Collaboration drives progress, and we need a solution that restores GCBASIC’s smooth integration.
Consider sticking with XC8 v3.00 for now if your projects don’t require the latest compiler features.
I’ll keep you posted on any workarounds or updates from the GCBASIC team to address this issue. In the meantime, share your thoughts, frustrations, or solutions below. Let’s tackle this together!
Evan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey everyone,
Big news from Microchip: they've released XC8 Compiler v3.10. However, for those of us relying on GCBASIC with PIC-AS, this update brings a major setback. Up until XC8 v3.00, GCBASIC enjoyed full integration with the compiler, making our workflows smooth and efficient. Sadly, v3.10 changes that.
The Issue
Microchip has removed internal device-support files from the compiler. Now, you must specify a Device Family Pack (DFP) using the -mdfp option for every project. This breaks the seamless integration GCBASIC had with PIC-AS up to v3.00, making it significantly harder to compile GCBASIC source code outside of MPLAB X or VS Code.
From Microchip’s release notes:
"The internal device-support files are no longer shipped with the compiler, and whenever you build a project, a DFP must be specified using the option. If you use the MPLAB X IDE or VS Code to build projects, you do not need to take any action, as the IDE will continue to manage DFPs for you. If, however, you build projects on the command line or via build scripts outside of an IDE, you will first need to download the appropriate DFP, unpack it on your build machine, and then specify the path to this DFP using the -mdfp option."
This means extra steps to download DFPs from Microchip’s pack repository and manually configure them. It’s a frustrating disruption, especially for those of us who loved the streamlined process with GCBASIC and XC8 v3.00 or earlier.
Why This Matters
This change feels like a step backward. It’s not clever, not smart, and definitely not collaborative. For the GCBASIC community, it undermines the full integration we’ve relied on, adding unnecessary complexity to our workflows. GCBASIC is all about making microcontroller programming accessible, and this update makes that harder.
What Can We Do?
If you use MPLAB X , you’re in luck—the IDE handle DFPs automatically so I just need to figure out the DFPs automatically. I think we have a tool that will do this but means more work, more maintenance and this will not be ready for many months.
For command-line users, you’ll need to manually download and unpack DFPs, then update your build scripts with the -mdfp path. Check the MPLAB XC8 C Compiler User’s Guide for details.
Raise your voice! Let’s share feedback with Microchip about how this impacts our community. Collaboration drives progress, and we need a solution that restores GCBASIC’s smooth integration.
Consider sticking with XC8 v3.00 for now if your projects don’t require the latest compiler features.
I’ll keep you posted on any workarounds or updates from the GCBASIC team to address this issue. In the meantime, share your thoughts, frustrations, or solutions below. Let’s tackle this together!
Evan
If you do need XC8 v3.10 then do this as a workaround.
Install XC8 v3.00 from
Then instal XC8 v3.10
Then create two symbolic links as follows:
mklink "C:\Program Files\Microchip\xc8\v3.10\pic\include\proc" "C:\Program Files\Microchip\xc8\v3.00\pic\include\proc" /Dmklink "C:\Program Files\Microchip\xc8\v3.10\pic\dat\cfgdata" "C:\Program Files\Microchip\xc8\v3.00\pic\dat\cfgdata" /DAnd, v3.10 will then compile.
This is a workaround until I figure out a method to locate the correct DFP file automaticaly.
See https://sourceforge.net/p/gcbasic/discussion/579125/thread/3c499bbd64/ for fix