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

Semi-automatic support of new devices #9

Open
rwirth opened this issue May 22, 2020 · 0 comments
Open

Semi-automatic support of new devices #9

rwirth opened this issue May 22, 2020 · 0 comments

Comments

@rwirth
Copy link

rwirth commented May 22, 2020

I am trying to build an avr-libc that supports new devices like the mega 4809. While the auto-generated IO headers are in place, there are (at least) some additional hurdles to overcome:

  • The device-specific directories below avr/lib are not generated by gen-avr-lib-tree because the list of devices is hard-coded.
  • Same thing for configure.ac, where each of the generated Makefile.am has to be added.
  • The iosym files for the new devices are missing, causing the CRT build to fail.

I think I have solved the first two problems by having gen-avr-lib-tree parse the spec-files used by the installed avr-gcc. The parse generates the same data structure that was used before. To tie the generated files into autotools gen-avr-lib-tree also generates an M4 file with an AC_CONFIG_FILES macro containing all generated files. That file can be included by configure.ac.

The missing iosym files could be added as stubs for now, they should probably be generated from the atdf files if I understand the process correctly.

I have created a branch in my fork that contains the changes.

Is this useful or are there issues that I have overlooked?

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

1 participant