-
Notifications
You must be signed in to change notification settings - Fork 77
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
tundra.syntax.install broken #248
Comments
You're right this is broken. The problem the extension key stuff is solving is that of filtering out unwanted input files by only picking up certain extensions. For example the C++ unit types use this to only pick up |
I was looking at this again today and I made a patch that removes the need for ExtensionKey ( accepts all suffixes when ExtensionKey is nil ). However it looks like there are some API changes that the install syntax was not updated for, which I currently do not have enough understanding of to attempt to fix:
Is there another way to copy DLL's into the target directory that I'm missing, which supports separate input paths for 32 and 64 bit builds? |
OK; that's going to require a bit more fixup. If the DLLs are built with Tundra you can override |
When using the install syntax extension I get an error message (it seems like it was not updated when an API breaking change was done before.). I am trying to use this feature for copying DLL's of third party dependencies into the output directory. Does anyone have a workaround for this?
The text was updated successfully, but these errors were encountered: