cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with app.mk using relative path to TouchGFX env folder

Jesper_MCI
Associate

Hi

I just noticed that when building the Simulator using TouchGFXDesigner 4.24.1 the files
/config/gcc/app.mk
and
/config/msvs/Application.props

are updated with the relative path to the TouchGFX env folder, for instance:

# Location of the TouchGFX Environment
touchgfx_env := ../../../../../TouchGFX/4.24.1/env

If I try to overwrite these paths the files are just overwritten when I run the Simulator from TouchGFX Designer.


This is a problem when working on a project with multiple people that may have the project check out at different folder depths. I don't think the solution is to require that the project is checkout out at the same folder depth for everyone on the same project.
You can argue that it isn't a big problem as TouchGFX Designer updates the path for anyone creating the Simulator.
But it does create 'noise' in the repository.

Any suggestions on how to solve this ?

//Jesper

1 REPLY 1
Pavel A.
Evangelist III

I don't think the solution is to require that the project is checkout out at the same folder depth for everyone on the same project.

Why? This is called "convention over configuration". What is good for one, is good for all. Everyone uses same settings, everyone is happy.

 'noise' in the repository

Specially to avoid unwanted changes, git has commit hooks. It is a script that can detect forbidden changes and fail pushes to the common repository. Or it can remove offending bits and continue.