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
[BUG] VC Redis .dlls are not beeing copied #79
Comments
@YehudaKremer I just confirmed the .dlls get packed using the MSIX tool. :) Thank very much for your fast fix! 🥇 One friendly, opinionated thought I had looking through this package: Small example: Future<void> copyVCLibsFiles() async {
const taskName = 'copying VC libraries';
_log.startingTask(taskName);
_vCLibsFiles = _getAllDirectoryFiles(
'${_config.vcLibsFolderPath()}/${_config.architecture}');
for (File file in _vCLibsFiles) {
await File(file.path)
.copy('${_config.buildFilesFolder}/${basename(file.path)}');
} using dart.io sync methods, I think most basic operations (read/write/delete) have sync versions. Maybe this could be utilized to get rid of some async stuff. :) void copyVCLibsFiles() {
const taskName = 'copying VC libraries';
_log.startingTask(taskName);
_vCLibsFiles = _getAllDirectoryFiles(
'${_config.vcLibsFolderPath()}/${_config.architecture}');
for (File file in _vCLibsFiles) {
File(file.path)
.copySync('${_config.buildFilesFolder}/${basename(file.path)}');
}
_log.taskCompleted(taskName);
} But this is really just the opinion of someone who was traumtized by dealing with a lot of race conditions haha. |
ℹ️ Info
Version:
v2.8.4
💬 Description
The VC .dlls are not getting copied. I stumpled upon this by testing a released Store App on a freshly installed Win 10 VM ... fml...
Before the .dlls where always copied. I unpacked the .msix with the MSIX tool and could verify that no VC .dlls are included. :(
This seems to be a regression of #30 . I can see that a test for this exists, so it seems very strange to me that this happens. I also verified that the VC libs are in the local msix plugin package.
BTW: Thank you very much for this package, it makes life much easier. 👍
📜 Pubspec.yaml
I use the --store flag to build for the store.
The configuration was working perfectly up to 2.8.0 or maybe 2.8.2.
The text was updated successfully, but these errors were encountered: