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

A relative path for an included resources is not found in the editor but is correctly used for target file generation. #161

Open
opcoach opened this issue Jan 20, 2025 · 4 comments

Comments

@opcoach
Copy link

opcoach commented Jan 20, 2025

If we include another tpd file with a relative path in the tpd editor, it displays an error :

Image

and the editor does not take it into account (it can not add the warning for doublons for instance).

On the other hand, if we generate the target file, the include is found and the target file is correct.

Remark : if we include a file from the same folder it works well.

The include's check in the editor should be updated to be able to navigate through relative paths.

@merks
Copy link
Contributor

merks commented Jan 20, 2025

I seem to recall some issues regarding whether the relative path is relative to the workspace logical location versus the underlying file system file locations. You've not really outlined the actual locations in the workspace nor in the underlying file system.

@opcoach
Copy link
Author

opcoach commented Jan 20, 2025

Hi Ed,

This is weird... in my existing project, it can't find a tpd file in a parent folder (../myfile.tpd) or in another relative path.

But if I create a new project with 2 tpd files, including with a parent link, the include is working...

Is there something specific stored in a project ? I closed it, restarted Eclipse, I still have the problem.

My relative path is for instance :

include "../../iaudit/zzz.brainwave.iaudit.tp/zzz.brainwave.iaudit.common.tpd" and of course I can access to this file when I am in the folder from where it is included.

@merks
Copy link
Contributor

merks commented Jan 21, 2025

It's impossible to comment without a concrete example that spells out what the structure looks like in the workspace and in the file system.

I'm not sure anyone will fix this problem for you. There's a handy Oomph setup:

https://github.com/eclipse-cbi/targetplatform-dsl/blob/master/CONTRIBUTING.md#setting-up-a-development-environment

I just tested that the setup works and that the builds still work.

Self-service is the best option here.

@opcoach
Copy link
Author

opcoach commented Jan 21, 2025

Yes I totally agree... I have a situation that works and one that fails ... I will try to find time to fix it or to investigate (even if it is not blocking) !

Thank you

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