Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version number on .xproject file does not match released version #78

Open
xross opened this issue May 25, 2021 · 1 comment
Open

Version number on .xproject file does not match released version #78

xross opened this issue May 25, 2021 · 1 comment

Comments

@xross
Copy link
Contributor

xross commented May 25, 2021

The .xproject file states version 5.0.0dc6fb354094

This has not been maintained, this is likely a general issue with lib_repos.

@lucianomartin
Copy link
Contributor

In infr_apps there is a script to update the Eclipse files:
https://github.com/xmos/infr_apps/blob/develop/lib/python/prepare_eclipse_files.py

In lib_i2c/lib_i2c there are 4 files that have not been updated recently:

  • .makefile: it is not used as far as I know, it has only some generic information, but no command to compile any code, its content is:
all:
    @echo "** Module only - only builds as part of application **"
 
clean:
    @echo "** Module only - only builds as part of application **"
  • .cproject: this file is used for Eclipse in XTC and updated by the script prepare_eclipse_files.py

-. project: this file is used for Eclipse in XTC and updated by the script prepare_eclipse_files.py

  • .xproject: this file contains info such as lib version, I assume it is used only in Eclipse, but I can't prove it. It is updated by the script prepare_eclipse_files.py as well

When I tried to run the script on my MAC laptop I had an error related to the missing Java version 1.6, as xTimeComposer requires it. This version was released in 2006 and on my machine I have a more recent version.

The complication of using such an old version of Java is that we should add the script prepare_eclipse_files.py to the Jenkins tests if we want to maintain those files, but the machines running the Jenkins test have a more recent version of Java.

As it is using such an old version of Java, I am wondering if it would be best to remove those files rather than to update them, but we need to find out who is using them first and check if it is ok to remove them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants