Why does nios2-bsp fail to look for .sopcinfo file when .ipx is used?

Description

Due to a problem in the Quartus® Prime Pro software version 17.0, when using an .ipx file to create multiple custom components, the .sopcinfo file is generated in the qsys_name folder and not in the project directory folder. 

When you are building a Nios® II application and bsp project in the Nios II Software Build Tools, you will see an error when you build the application project.

Error:

Info: Compiling ../src/main.c to obj/default/main.o

nios2-elf-gcc -xc -MP -MMD -c -I../bsp/HAL/inc -I../bsp -I../bsp/drivers/inc  -pipe -D__hal__ -DALT_NO_C_PLUS_PLUS -DALT_USE_DIRECT_DRIVERS -DALT_NO_INSTRUCTION_EMULATION -DALT_USE_SMALL_DRIVERS -DSMALL_C_LIB -DALT_SINGLE_THREADED    -O2 -g -Wall   -mno-hw-div -mno-hw-mul -mno-hw-mulx -mgpopt=global  -o obj/default/main.o ../src/main.c

../src/main.c:33:38: fatal error: custom_pattern_generator.h: No such file or directory

 #include "custom_pattern_generator.h"

                                      ^

compilation terminated.

make: *** [obj/default/main.o] Error 1

make: Leaving directory 

Resolution

To workaround this problem, copy the qsys_name.sopcinfo file in the qsys_name folder into the project directory which has the same path with where the <component name>.ipx file is located and rebuild the application file in the Nios II Software Build Tools. 

This problem is scheduled to be fixed in a future release of the Quartus Prime Pro software