Recently I had a computer failure that resulted in reinstalling the windows operating system. Fortunately, I was able to back up my machine before doing the reinstall. However, I am now trying to make my CoDeSys project compile but I can't seem to figure out how to make CoDeSys recognize the libraries located in C:\ProgramData\CODESYS\Managed Libraries\. Before I reinstalled the operating system I was able to back up the managed libraries directory and now I have copied the directory back to the C:\ProgramData\CODESYS\Managed Libraries\ location. I can see the CODESYS library files in the directory through the file explorer but CoDeSys does not recognize them.
I have attempted to add a repository location using the library repository but I when I add a dummy location it won't let me delete the original location (to then re-add it).
I am using CoDeSys 3.5 SP11 Patch 4. I understand this is not the newest version of CoDeSys.
Thanks
It is not enough to copy libraries to this catalogue.
You need to install package with all hardware from your supplier.
What you have to do is download the .package file from supplier of your hardware.
Then you have to open codesys go to tools -> package manager -> install.
After that library will be installed properly.
Please take a look for this youtube movie if I didn't explain it well.
https://youtu.be/GFkA4E1R4aQ?t=393
Cheers!
Related
How to get the exe from https://github.com/tsenart/vegeta/releases in order to test in windows?
This says I could find the .exe in this link but I don't.
I am trying to load test the apis in windows, as a start.
I do no know Golang and this project is developed using Go.
I would appreciate any directions on how to go about this. Thank you
For this version they didn't provide an executable for windows. If you check one minor version lower you find a .zip with an executable in it. If you need v12.8.4 you could write the people of the repository or just compile the code by yourself.
It looks like they only have executables ready to download for MacOS and linux on the newest version.
Version 12.8.3 however has a windows download.
I'm currently trying to learn Assembly for x64 Windows. I tried the example code from this Intel website,
but whenever I try to compile it with the command given in the document:
ml64 hello.asm /link /subsystem:windows /defaultlib:kernel32.lib /defaultlib:user32.lib /entry:Start
I always get an
LNK1104 error
I know that it means the compiler can't find the library file, I googled the problem and quickly found that I need Visual Studio with Windows SDK, which I downloaded and installed. But still can't find a kernel32.lib or user32.lib in any files other than the Windows system files.
I tried everything and I simply can't fix it. I hope someone could help figure this out.
There is a well-known MASM32 SDK available created by hutch--. This package contains the requested libraries in a (legacy) 32-bit version.
But there is also a 64-bit update of that famous package by hutch--:
Current build of the 64 bit MASM SDK.
It should contain the .inc and .lib files you need and more...
This is the current build of the 64 bit MASM SDK. This one is a lot closer to complete and with the correct Microsoft binaries added to it, it is capable of building a wide array of application types. It can be use in 2 different ways, it should be unzipped from the root directory of the partition that it is being installed on. You can either manually add it to an installation of the MASM32 SDK OR you can install it on a partition that does not have MASM32 on it and simply rename the buildx64 directory to MASM32. Installing it on another partition is the preferred technique as QE has its menus and accessories set up for building 64 bit code.
You still need to add the Microsoft binaries which would typically be from an installation of vs2017 or from an earlier version for Win7 64. In the bin64 directory there is a file called "Microsoft_File_List.txt" which shows the files you need. The list is from the current version of Visual Studio 2017 version and if this is the version you have, use the ML64 from the "x86_amd64" directory that is 402,584 bytes in size.
In the "buildx64" directory is a batch file called "makeall.bat". This must be run to build all of the libraries and include files.
They are the gold standard of Windows assembly developing.
I'm new to OSX and i'm getting used to the way frameworks work.
In c++ projects, when i want to link a preinstalled framework, for example OpenGL.framework, i just type "-framework OpenGL" and i'm good to go.
On the other side, when i copy a new framework into for example /Library/Frameworks, and i go "-framework MyFramework", the framework is not linked properly. Eclipse doesn't find the file. I also add "-F/Library/Frameworks" but still it doesn't find it.
Do i have to do something else than copying the framework to the folder?
If you haven't rebooted since installing the framework, you might have to update the shared library cache manually:
sudo update_dyld_shared_cache
The other option is to reboot. To make completely sure that the frameworks will be rescanned, you can touch the directory containing them first:
sudo touch /Library/Frameworks
sudo reboot
If this does not work, it is likely that the framework you installed is not properly formed. The directory structure, plist file, etc, need to follow a set of rules to form a framework.
When you install your product locally, all the needed files are stored in the machine.
When you set the features to Advertise, files will be installed locally when the user launches the application.
What happens then when yo set the features to "run-from-source"? I Googled it and was only able to find this: http://msdn.microsoft.com/en-us/library/aa367538%28v=vs.85%29.aspx
Thanks!
This is a rarely used feature of Windows Installer and I don't normally reccomend using it. It was invented back in a day when hard drives were small and the thought was you 'advertised' ( pretend install aka install source ) a feature and that when the user clicks the shortcut it would go to the source and finish the installation of the feature ( aka install local )
It just adds a lot of complexity to your servicing model. It's not worth it IMO.
When placing all installation files next to the MSI (similar to advertised installation), you can install features from source. This means that all files in these features will be used from the MSI location (they are not copied in the target folders during install).
Running from source can be used when the installer remains permanently on the target machine. So the application can use the installer directly instead of using installed files.
I had developed a small program in netbeans using c++. I need to know how can i deploy/run the package on another linux system
Abdul Khaliq
I have seen your code, you probably missing XML files in the current folder... where the executable is located... paste then and then run as ./your-executable
I recommend that you use a makefile to recompile on your target machine which will ensure that your program is deployed properly.
You should use a makefile as suggested. I know that NetBeans can generate one, but it's been a while since I last did so. Maybe this can help: http://forums.netbeans.org/topic3071.html
Typically, once compiled, your executable will need several libraries. Chance is that those libraries will also be available on the target linux system.
Thus, you can simply copy your executable over to the other system. If you run ldd on your executable, you should see the list of libraries your executable is dynamically loading. Those libraries should be available on the target system as well.
In case your executable makes use of resources such as images and other binary files, you can use a resource system (e.g. Qt Resource System) and compile those binary files into your executable.
The easiest way to test is to do the copy, run
ldd yourExecutable
on the target system. It will tell you if you are missing any library. Install those libraries using the system package manager.
Of course, you also have the option to statically build all libraries into your executable. However, this is not recommended since it makes the executable too large and complicates matters.
What type of package is your netbeans compiler creating? deb,rpm? If you are moving the package to a different linux install you will need to use that distributions package type. Ubuntu - deb
Fedora/Redhat - rpm
etc...
I'm not sure how you change this in netbeans but I'm pretty sure it has the ability to. A google search could help you more.