Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
12747 Discussions

C2H and source/version control problem

Altera_Forum
Honored Contributor II
1,056 Views

I'm currently paring down my Quartus/NIOS projects to put into a CVS source control system. I've got things reduced to the bare minimum (I think) but I'm running into an issue with C2H. Unfortunately, C2H uses the project name as part of the SOPC block. If someone starts a new NIOS IDE project based on the existing Quartus project then C2H is going to want to regenerate the C2H SOPC component with the new project name and I end up with two C2H blocks in the SOPC design. 

 

From a source control perspective I seem to have these options: 

 

1) Check in a version without any C2H blocks and let each developer regenerate what they need when they run C2H the first time. (Problem: each time SOPC or NIOS project gets committed we have to make sure C2H blocks are removed) 

 

2) Check in a version with C2H blocks and make sure each developer understands they might have to go into SOPC builder and delete the stale C2H component. (Problem: unnecessary burden on developers and effectively impossible to have a developer use only NIOS II IDE without Quartus) 

 

Either version is ugly, I'm wondering if someone has a better idea? 

 

Thanks, 

Andrew
0 Kudos
0 Replies
Reply