I have released a windows app using windeployqt. It works everywhere except on one PC. On that PC (Windows 10 Pro) the app runs (I can see it from the Task Manager) but UI is not shown.
These are the steps I do to release the app:
rmdir /S /Q install
mkdir install
copy "build\Desktop_Qt_5_14_2_MinGW_64_bit\Release\release\MyApp.exe" install
C:\Qt\5.14.2\mingw73_64\bin\windeployqt.exe --qmldir qml install\MyApp.exe
copy "C:\Qt\5.14.2\mingw73_64\bin\libgcc_s_seh-1.dll" install
copy "C:\Qt\5.14.2\mingw73_64\bin\libstdc++-6.dll" install
copy "C:\Qt\5.14.2\mingw73_64\bin\libwinpthread-1.dll" install
pause
Am I missing something? Thank you
Related
I'm trying to run my dotnet 5 single file app with Alpine Linux docker image.
This is my Dockerfile
FROM mcr.microsoft.com/dotnet/aspnet:5.0-alpine
WORKDIR /app
COPY ["Service.Translations", "/app/Service.Translations"]
CMD ["./Service.Translations", "--urls", "http://0.0.0.0:5000"]
This was framework-dependent app. Also tried with self-contained and result is the same:
not found. Dotnet doesn't see my file and sh doesn't see too.
Is it problem because I built my app on Windows? All tutorials with alpine compile app inside image. If I change Alpine to Ubuntu or smth else - everything is ok.
UPDATE:
Ok, problem was with publish. I had to change --runtime to linux-musl-x64 instead of linux-x64
I found the problem. Alpine Linux uses musl c library and it makes standard dotnet build incompatible with this linux distro. Visual studio doesn't have all publish runtime options. Here https://learn.microsoft.com/en-us/dotnet/core/rid-catalog you can find all of them. So for alpine linux we have to use linux-musl-x64 runtime instead of linux-x64
I installed heroku cli on windows 10 via exe installer.
When i try to run heroku --version command or heroku login
command, the command window does not respond. It does not give any error.
Then i uninstalled it and installed it using npm install -g heroku-cli
but getting same result.
Node version - 8.7.0
In Windows cmd prompt, do:
echo %USERPROFILE%
Go to your C:\Users\YOURNAME
Look for a file named:
_netrc
This file stores login credentials. Delete it.
Then check for an update:
heroku update
Then try to log in:
heroku login
I saw some people create an environment variable called HOME and add the path to YOURNAME so the environment knows to look for the _netrc file there.
Other trouble-shooting ideas if the above doesn't work for you can be found at Heroku CLI troubleshooting
In windows , run %LOCALAPPDATA%\heroku, completely delete this folder. and check again on cmd by typing heroku --version. Hope this helps.
I ended up uninstalling heroku from the Windows Installer and instead used the standalone tarball.
You can get the tarballs from here.
After you downloaded and extracted it, you can go to your terminal and cd into the directory where you extracted the file and do the following command:
./bin/heroku --version
Whenever you need the heroku CLI, you can cd into the directory where heroku is, then ./bin/heroku is the executable for heroku.
I’m trying to get sqlite3 to work in an electron app running on Windows7 and 10. Running the following command, I was able to create electron-v1.7-win32-x64\node_sqlite3.node
cd node_modules/sqlite3 && sudo npm install nan
&& sudo npm run prepublish && sudo node-gyp configure --module_name=node_sqlite3 --module_path=…/lib/binding/electron-v1.7-win32-x64
&& node-gyp rebuild --target=1.6.11 --arch=x64 --target_platform=win32 --dist-url=https://atom.io/download/atom-shell
--module_name=node_sqlite3 --module_path=…/lib/binding/electron-v1.7-win32-x64
However, I get Uncaught Error: %1 is not a valid Win32 application. \\?\c:\folder\ppt_win32-x64\resources\app\node_modules\sqlite3\lib\binding\electron-v1.7-win32-x64\node_sqlite3.node.
My node version is v7.4.0. Electron v1.6.11.
I was trying to compile for windows from mi Mac and I had that problem too, but after some readings I figured out how to proceed, and after all I can say that I got it. Yesterday I spent all day setting up a windows virtual machine in my (other) Linux laptop (I used my linux laptop just because my mac was exhausted in storage...). I was having too a problem with the preloadScript from electron main process in windows, Cant found the script, it was solved too.
Anyway, I think the library node printer from #tojocky is well maintained, in other hand in the electron-builder documentation they say that you should compile in native for natural reasons. Once you will have it, you'll see that it's a cleaner and pragmatic solution ...
This was my entire process, I hope it helps to someone having the same issue:
Get VirtualBox (or Parallels but is not free)
Get iso for W10
Create a VM with this W10 iso, and you should give to this VM some storage (because some dependency that you'll need to compile), I have assigned 60gb to this VM
Once I had that VM running, I just installed in that machine Visual Studio 2017 (with their build-tools included, it's necessary)
And then, I used CMD to make the rest
Install NodeJS (and NPM, but it comes with)
Install node-gyp globally
Install Python 2.7
Clone your project from git (in my case)
npm i (in your project), you should have as npm dependency in your package.json the module electron-builder of course. (here I had some troubles because when node-gyp tried to rebuild printer to generate the binary for windows it was failing, this was because it was imposible to find the python executable, so if you face this problem you should add it like:npm config set python "c:\Python27\python.exe" in my case )
Then try again npm i and Voila!
If you still having error you can rebuild the native dependency as well, run:
node-gyp rebuild --target=YOUR_ELECTRON_TARGET[eg: 1.8.4] --arch=YOUR_ARCH_TARGET[eg: x64 | ia32] --dist-url=https://atom.io/download/atom-shell
After all, you should make the build using electron-builder, in my case my npm script command was build --win --x64 but you can use the --ia32 flag as well for 32bits
I am trying to run a Qt app in docker. I have a very limited Linux experience. The OS is centos. Qt version is 5.9.1. The overall idea is to run it in Xvbf. (I have already run firefox in DISPLAY:1(Xvbf) inside docker under centos)
When I try "docker run -it myTestGuiApp", I get an error libGL.so.1: cannot open shared object file: No such file or directory.
What is missing here?
Thanks in advance.
You probably have a missing library. You might need to install this : yum install mesa-libGL
Just add this line in your dockerfile : RUN yum install mesa-libGL
If this doesn't work, copy here your dockerfile.
from //build, i see the coolness of running nodejs and asp net 5
i am trying to use vscode to run some basic C# console app. how should i config the task to build and run/debug it? is there any sample?
The yeoman aspnet generator has a ConsoleApplication template that will work in VSCode.
Install ASP.NET and DNX (according to your OS see the instructions here: https://code.visualstudio.com/Docs/ASPnet5)
Install yeoman dependencies and generate a yeoman aspnet project (choose Console Application)
npm install -g yo grunt-cli generator-aspnet bower
yo aspnet
cd to your project dir you just created and:
dnu restore
Now you can open the dir in VSCode. Open the command palette (command-shift-P) and type run
EDIT:
Note however that while mono-based C# debugging works in Linux and OSX, ASP.NET 5 debugging does not yet work in the preview version.