![]() ![]() and this does not create setup.ini either.įinally I found that mentioned the switch -okmissing required-package - so, finally this command: $ mksetupini -arch x86_64 -inifile=x86_64/setup.ini -releasearea=. ![]() Mksetupini: package '' version '-1bl1' depends nonexistent or errored package 'cygwin' Mksetupini: package '' version '-1bl1' requires nonexistent or errored package 'libreadline7' Mksetupini: package '' version '-1bl1' requires nonexistent or errored package 'libgcc1' Mksetupini: package '' version '-1bl1' requires nonexistent or errored package 'cygwin' noarch/release/base-files but has files: noarch/release/base-cygwin but has files: noarch/release/adwaita-icon-theme but has files: adwaita-icon-theme-3.26. $ mksetupini -arch x86_64 -inifile=x86_64/setup.ini -releasearea=. I am using a script like this to prepare the directory for setup #!/bin/bash $ cygcheck -f /usr/bin/mksetupiniĬreate a website directory similar to the cache you have from downloading, make a ARCH/release directory and copy the content of dist for the packages you are interested. You can create a local setup structure, and use the calm package to create Ĭygport is the tool to build packages that can be installed with Cygwin setup-$ARCH.exe installation. If I "install" by just unpacking into the Cygwin root filesystem, how do I "uninstall" then?ĭoes cygport change installation paths in respect to make install of the package? If not, then I guess make install is an option, because then I should have make uninstall too. So, now I have and packaganame.hint - can't I use these with the Cygwin setup-x86_64.exe program (so that I'd have a marked entry, when I look up the package name in setup)? Install' or simply run it from the build directory :-) You could install yourself or by descending to the build directory and doing 'make So for most cases, it works just fine just to unpack the archive into the I have built a package from using cygport however I just noticed that cygport install command does NOT install in the cygwin filesystem, but in a subdirectory of the source build directory as such, executables are not in the cygwin path, and you cannot call them by name. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |