You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 28, 2024. It is now read-only.
We are aiming to use the NcDataReader2 library in the AixLib (RWTH-EBC/AixLib#313). Since we found some improvement regarding the annotation to include external files, it is not necessary anylonger to copy the files into the working directory.
The annotation is like: Include = "#include <ncDataReaderEA.h>", IncludeDirectory = "modelica://NcDataReader2/Resources/Include",
Especially the ...Directory commands are not implemented in the current master.
Similar, but with focus on 32 bit, is done in BuildingSystems: https://github.com/UdK-VPT/BuildingSystems/blob/master/BuildingSystems/Utilities/NcDataReader2/ncEasyGet1D.mo
Additionally, due to the 32/64 bit folder structure, the correct files will be chosen.
This was tested with Dymola 2017.
We could also create our own solution like in BuildingSystems. But in my opinion it is better to keep the dependency to this repo in order to stay up to date.
Is it okay, if we fork a branch and make a PR afterwards?
The text was updated successfully, but these errors were encountered:
We are aiming to use the NcDataReader2 library in the AixLib (RWTH-EBC/AixLib#313). Since we found some improvement regarding the annotation to include external files, it is not necessary anylonger to copy the files into the working directory.
The annotation is like:
Include = "#include <ncDataReaderEA.h>", IncludeDirectory = "modelica://NcDataReader2/Resources/Include",
Especially the
...Directory
commands are not implemented in the current master.Similar, but with focus on 32 bit, is done in BuildingSystems: https://github.com/UdK-VPT/BuildingSystems/blob/master/BuildingSystems/Utilities/NcDataReader2/ncEasyGet1D.mo
Additionally, due to the 32/64 bit folder structure, the correct files will be chosen.
This was tested with Dymola 2017.
We could also create our own solution like in BuildingSystems. But in my opinion it is better to keep the dependency to this repo in order to stay up to date.
Is it okay, if we fork a branch and make a PR afterwards?
The text was updated successfully, but these errors were encountered: