CODEWITHSUNDEEP
iar
Amal
Amal

Reputation: 1

IAR Failed to generate browse indexing file, paths are too long

I'm observing these errors in Source Browser Log in IAR Embedded Workbench 9.20.1 when opening my project Logs: Source Browse Log created. Launching source browser The browse files cannot be generated at /../ , paths are too long. Please move the browse info folder. Failed to generate browse indexing file.

Is there any solution for this problem, knowing that I don't had this error using older version of IAR.

Many Thanks!

This error appear when opening the project. Fatal error while generating source browse information.

Upvotes: 0

Views: 2540

Answers (4)

Frederick Herrmann
Frederick Herrmann

Reputation: 1

In my case, the simple fix was to just change a backslash to a forward slash in Project Options → General Options → Output Directories → Browse files.

The project file created by STM32CubeMX had set it to MyProject\BrowseInfo.

The indexing problems went away after I changed to MyProject/BrowseInfo.

This was with STM32CubeMX V6.3.0 and IAR EWARM 9.50.2.

Upvotes: 0

iamnagaky
iamnagaky

Reputation: 1143

I was using IAR for RX 4.20.3 & was facing error in indexing files. The reason was that I was using a 'ø' character in the folder path of the mentioned project. Something like mentioned below,

D:/User_xxx/Folder_with_ø/Project.eww

After removing the character, parsing was working fine.

Upvotes: 0

Simão Ribeiro
Simão Ribeiro

Reputation: 11

I also currently faced an issue with Browser information that never stopped and it was related with a "&" on a project folder name.

I removed it and now I don't face any issue.

This happened also migrating from v8 (no issue) to v9 (with issue).

Upvotes: 1

felipe-iar
felipe-iar

Reputation: 45

The Source Browser settings have changed in the later IDEs (v9+).

Earlier versions of the IDE had their Source Browser information stored in the "Object Output Directory" ($OBJ_DIR$, set in the Project Options → General Options → Output Directories → Object files).

In general, this would mean (e.g., for the Debug configuration):

$PROJ_DIR$/Debug/Obj

In which any argument variables ($xxxxx$) would expand into the corresponding full path name.

In v9+ IDEs, the Source Browser output offers a specific setting for "Browse files" (defaults to "Debug/BrowseInfo") in the same project options page. Effectively, the setting will point to:

$PROJ_DIR$/Debug/BrowseInfo

This means that, the full path name resulting from the argument variable expansion also becomes longer and, depending on how deeply the project files are stored in the file system, might end up exceeding the maximum allowed resulting path length (~250 characters).

One workaround might be to use the User's temporary folder (%TEMP%) for storing these generated files. In order to express the Windows environment settings in the IDE, the variable must be expressed as $_TEMP_$.

One example for settting the "Browse files" field (Originally Debug\BrowseInfo):

$_TEMP_$\$PROJ_FNAME$\$CONFIG_NAME$\BrowseInfo

Or any other variation that would make sense for keeping the resulting full path from exceeding the operating system's limitations.

After changing the parameter, Project → Clean Browse Info can discard the previous information and recreate the index.

More on the IDE's Argument Variables can be found here.

Upvotes: 2

Related Questions