Application: Cygwin
Category: Utilities
Description: Cygwin is a collection of tools which provide a Linux look and feel environment for Windows using a DLL (cygwin1.dll) which acts as a Linux API layer providing substantial Linux API functionality.
Download Cygwin 1.7.34 Development Test 1 [427 KiB download / 126 MiB installed]
Download Cygwin 1.7.34 Development Test 1 (32bit) [427 KiB download / 126 MiB installed]
Github Repository:
https://github.com/thasmo/portableapps.cygwin
Release Notes:
1.7.34 Development Test 1 (2015-02-07): Changed to a hopefully more reliable mirror. Updated the terminal startup script based on the latest Cygwin changes.
1.7.32 Development Test 1 (2014-09-10): Changed the mirror protocol from FTP to HTTP for downloading packages.
1.7.28 Development Test 1 (2014-02-13): Removed md5 hash to disable file integrity check of the Cygwin installer after downloading it. This helps for not updating the portable version everytime a new version of Cygwin gets released.
1.7.27 Development Test 1 (2013-12-20): Added a 32bit version. Yay!
1.7.25 Development Test 3 (2013-11-24): Changed the Cygwin mirror and configured the setup to run without needing administrator privileges. Also updated the MD5 checksum because it seems the Cygwin setup.exe file has been changed/updated although no new version was released.
1.7.25 Development Test 2 (2013-10-14): Correct the MD5 checksum.
1.7.25 Development Test 1 (2013-10-06): Update Cygwin to 1.7.25.
Development Test 9 (2013-08-12): Update Cygwin to 1.7.23.
Development Test 8 (2013-07-22): Update Cygwin to 1.7.22 64bit.
Development Test 7 (2013-06-09): Various small tweaks.
Development Test 6 (2013-03-30): Upgrade won't overwrite existing cygwin files. Cygwin setup.exe and packages will be downloaded during the installation process.
Development Test 5 (2012-12-29): Fixed issue with wrong relative path →
Development Test 4 (2012-12-28): Prevent deleting the home directory when upgrading
Development Test 3 (2012-12-27): Fixed issue regarding spaces in the path →
Development Test 2 (2012-12-12): Minor improvements →
Development Test 1 (2012-12-10): Initial release
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Nothing major, but just some things that you should update to meet the format spec:
I haven't run it so no comments yet on portability/workingness, but I will try it out as time permits and get back to you.
Thanks a lot for your feedback, really appreciate it.
Going to have a look at it as soon as possible!
Incorporated all your feedback. Curious about someone trying it out. I'm no linux pro, so I would be glad for feedback about the initialization scripts etc. to further improve things. Thanks!
Thank you for your efforts.
I've just downloaded and installed vDevTest2.
This is exactly what I've been looking for such a long time.
Awesome! I'd be really happy about feedback on this - just drop some lines if you feel like sharing your thoughts. Thanks!
Anyone tried it yet? Anyone interested? :>
My cygwin directory has some spaces so I edited some files.
File1 : CygwinPortable\App\AppInfo\Launcher\CygwinPortable.ini
[Launch]ProgramExecutable=Cygwin\Initialize.bat
RunAsAdmin=compile-force
HideCommandLineWindow=false
:: launch Initizlize.bat instead of terminal.bat
File2 : CygwinPortable\App\Cygwin\Initialize.bat
@ECHO OFFSET CYGDRIVE=
SET DRIVELETTERS_=ZYXWVUTSRQPONMLKJIHGFEDCBA
:CHECKDRIVE
SUBST %DRIVELETTERS_:~0,1%: "%CD%"
IF "%ERRORLEVEL%"=="1" (
SET DRIVELETTERS_=%DRIVELETTERS_:~1%
IF "%DRIVELETTERS_%"=="A" (
ECHO NO AVAILABLE DRIVE!
PAUSE
EXIT
)
GOTO :CHECKDRIVE
)
CD /D %DRIVELETTERS_:~0,1%:
SET CYGDRIVE=%CD%
SET DRIVELETTERS_=
START /B /WAIT App\Cygwin\terminal.bat
SUBST %DRIVELETTERS_:~0,1%: /D
:: Make a new drive mounted Cygwin folder and run terminal.bat
:: When exit Cygwin that drive will be removed
File3 : CygwinPortable\App\Cygwin\terminal.bat
@echo OFF@REM Paths
SET CYGROOT=%cd:~0,-1%
@REM SET CYGROOT=%CYGROOT:App\Cygwin\=%
SET CYGDRIVE=%~d0
@REM Environment variables
SET PATH=%PATH%;%CYGROOT%\App\Cygwin\bin
SET ALLUSERSPROFILE=%CYGROOT%\Data\ProgramData
SET ProgramData=%CYGROOT%\Data\ProgramData
SET CYGWIN=nodosfilewarning
@REM Login credentials
SET USERNAME=One
SET HOME=/home/%USERNAME%
SET GROUP=None
SET GRP=
@REM User setup
IF EXIST %CYGROOT%\App\Cygwin\setup.sh (
%CYGROOT%\App\Cygwin\bin\bash %CYGROOT%/App/Cygwin/setup.sh
) ELSE (
%CYGROOT%\App\Cygwin\bin\bash
)
@REM Start the terminal
@REM %CYGROOT%\App\Cygwin\bin\mintty
Exit
:: no setup.sh files option
:: no need second cygroot variable setting.. actually
and I have a question!
How can I Set My Cygwin
Initial PATH : HOME
and run .profile .bashrc ... etc files
please help me
What exactly is the problem with the spaces in the cygwin path? Could it just be escaped somehow?
with the origin script 'terminal.bat', it occurs an error message like this. (it is an example. with space)
---------------------------
E:\Documents
---------------------------
Windows cannot find 'E:\Documents'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.
---------------------------
:: I use Korean version WinXP Pro SP3 so I translated below message.
---------------------------
E:\Documents
---------------------------
'E:\Documents'을(를) 찾을 수 없습니다. 이름을 올바르게 입력했는지 확인하고 다시 시도하십시오. 파일을 검색하려면 [시작] 단추를 클릭한 다음 [검색]을 클릭하십시오.
---------------------------
That Directory should be 'E:\Documents and Settings\One\My Documents\Downloads\CygwinPortable'
but it is cut off at the first space of the path.
so, I modified script terminal.bat, first, all path variables with double quotations.
like this, %cd% -> "%cd%", %PATH% -> "%PATH%"
but that double Quotations were piled on and on
"C:\Some Dir" -> ""C:\Some Dir"" -> """C:\Some Dir"""
and i've got error.
So I made a script to make Cygwin Directory short and not spaced with subst command.
and no error occurs any more
but the startup directory is '/cygdrive/z'
and any source files(profile, bashrc, inputrc etc) are not applied.
do you have some clues or hint for me?
)
(I'm so sorry for my bad English.
+
with setup.sh file,(what ever commands in it or even no command)
not any thing done...
just flash image appears and disappears. that's all
++
it's perfect(i think) on non-spaced path
Could you please test the new version, Development Test 3? Thanks!
Thanks for your effort
It's so clear and cool!
I LOVE IT ! XD
In terminal.bat script
"%CYGROOT%App\Cygwin\bin\bash" "../setup.sh"It occurs error on command prompt
/usr/bin/bash: ../setup.sh: No such file or directoryplease test with adding "pause" command next to that "...setup.sh" line
I changed "../setup.sh" to "App/Cygwin/setup.sh"
"%CYGROOT%App\Cygwin\bin\bash" "App/Cygwin/setup.sh"and, No errors.
Have a Good day
Plus, If I don't want to Use mintty.exe but just command prompt(cmd.exe)
what can I do?
Thanks, should be fixed.
If you wanna use cmd.exe you may edit terminal.bat and
change the path from mintty.exe to your cmd.exe program.
Thank you
.
Check update.bat please
spaced path error
if add double quotations, START~~~ line got error with options
cmd says ::cannot find '--no-shortcuts' file!
but that's not file
START /B %CYGROOT%App\Cygwin\Cygwin.exe ^
--no-shortcuts ^
--disable-buggy-antivirus ^
--root %CYGROOT%App\Cygwin\ ^
--local-package-dir %CYGROOT%Data\Packages\
--> spaced path error
START /B "%CYGROOT%"App\Cygwin\Cygwin.exe ^
--> option error
Hi!
Should one of the principles for PortableApps be that they don't write persistent information to
the system? I have this observation about Test 5
{CygwinPortable_1.7.17-1_Development_Test_5_English.paf.exe}.
After experimenting with it (heh, first of all, I am very happy!) I discovered that it is leaving
behind traces of itself in the Registry.
The keys it is writing include HKCU\Software\Cygwin\Installations.
The full Registry entry looks like this:
As you would expect, there is also a corresponding key
HKLM\SOFTWARE\Cygwin\Installations. One for the HKCU hive and one for HKLM.
After digging a bit I found out that this has a purpose, one which is important to portable
Cygwin, and which dates from 2009. http://cygwin.com/ml/cygwin/2009-11/msg00067.html
I have an existing Cygwin installation on the machine where I am using PortableCygwin. So there
are multiple entries for the keys.
Based on even a quick reading of the cited mailing list info, it seems clear that the solution
wouldn't be as simple as forcing cygwin's DLL to not write the Registry keys. They are needed.
Also, clearly, these keys need to be removed when the Cygwin session is closed, when the
PortableApp Device is removed, or at some suitable point.
Your opinion, Thomas?
Best Regards
Second this. It's not "portable" if it works with registry entries on the host computer. Does this mean it won't work if I plug my flashdrive into a different computer? I thought that was the whole point.
This comment was made two years ago, but got no followup. Is there any solution?
True, this is still an open issue which needs to be dealt with and for which I didn't have time yet. I'm using Cygwin Portable from within my Dropbox folder on two different machines without any major problems. I can remember that I fiddled around, years/months ago, with determining which registry entries Cygwin uses but in the end I wasn't able to make any progress on this. The project is hosted on GitHub and if anybody wants to contribute on this, I'd be happy to merge a fix which solves this open issue. For now I can't provide a proper solution for this, sorry.
Hi,
The generated file that are named /etc/passwd and /etc/group should be
empty files in the distribution PAF.
Another file of importance is /etc/fstab and that one should be in a clean state
when distributed.
Ciao!
I've been using http://symbiosoft.net/projects/cygwin-portable to install a portable cygwin and then use the setup tool to upgrade it. It's been serving me for years, however there are issues here and there and a new up to date package is greatly appreciated! Thanks.
I noticed a few of the issues already reported, but one that I think I am first to report, is when "upgrading" using the paf file. If you use the paf file more than once it goes ahead and wipes clean the old installation (or so it seems), then reinstalls what is included in the installer. This shouldn't happen.
For Cygwin, I think one just needs an initial installation and then he should upgrade via the Cygwin setup utility, as you very nicely provide for in your PortableApp. However, your installer should either detect an existing installation and abort, or upgrade only selected files that you are creating specifically for the portable version of Cygwin, without touching the user's existing Cygwin.
You are currently assuming that the user makes all customizations in his user homedir, but that can't be the case, because there are tools writing in /etc and so on, that can't be ignored. There will also be plenty of changes happening throughout use of the Cygwin installation.
It may also be useful to point the user to the terminal.bat where he can change the default user and homedir, alternatively it may be more convenient to automatically detect and set the username in that file while installing.
Hi - returning after my last posting which February 20, 2013. I'm going to post now to make a meta- type observation about this project.
The project manager, thasmo, last posted an update on 2012-12-29 (Development Test 5). He has not responded here on the forum to any messages since December 29, 2012. Also, his homepage link has never worked since I began reading the PortableApps forum. (Try it).
By acceptable Open Source on Internet criteria, this project is dead. It's now AbandonWare, meaning it is "up for grabs," as Americans say. Portable Cygwin is a very good idea, and Development Test 5 was getting close but with some important unresolved issues. It definitely was not close to meeting what I understand to be PortableApps.com spec for an official non-development "Release."
Is anyone motivated to take up this project, deal with the issues I and others have noted on this forum, and make a new dev release, with a plan to release an Official PortableApps Cygwin some day?
Ye, I'm sorry for the long delay of releasing a new version. For now there's a new version with some improvements which were mentioned here.
Installation/Upgrade shouldn't overwrite the existing files inside the App\Cygwin directory so you're safe to update. I also changed the overall installation process. Now the Cygwin setup (setup.exe) will get downloaded throu the installation process and will be run at last step of the installation. This also means that the packages won't be delivered with the new installer; they will be downloaded during the installation of Cygwin.
The project is hosted on Github now:
https://github.com/Thasmo/portableapps.cygwin
I'm happy to receive feedback, pull requests, bug reports, etc.
All relevant details/links are updated above.
Is there a way to execute terminal without admin privileges ?
Actually not, I think, because the "run as admin" option is set when compiling the launcher. But you can look into the file "App\Cygwin\terminal.bat" which launches the terminal.
You could create your own *.bat file and launch the terminal:
START "Cygwin Terminal" /B "%CYGROOT%App\Cygwin\bin\mintty.exe" "-"
I'm not sure why I set this to be executed as admin, but I will have a look later if it's still needed.
This issue is occuring when I attempt to install this package - also when I download the source from github and build the paf from it.
The portable app installs fine for me, but afterwards I can't install any more applications (I've tried several, none work) - I get the following error:
Error on update, cygutils.sh exit code 127
In /var/log/ I see the following error:
/etc/postinstall/cygutils.sh: line 2: /usr/bin/update-mime-database: No such file or directory
Googling around finds this:
http://cygwin.com/ml/cygwin/2013-05/msg00211.html
Where it's stated that this is a known issue that occurs if cygwin is installed without python. I've been digging through the package files to see if I can modify a setting in the in the source to include python in the initial installation - no luck so far, not sure if it'll fix it. Any ideas?
Just in case anyone else is having this problem - I attempted to modify the .nsh file with the following:
[code]!macro CustomCodePostInstall
ExecWait '"$INSTDIR\App\Cygwin\Cygwin.exe" --quiet-mode --no-shortcuts --disable-buggy-antivirus --site http://cygwin.xl-mirror.nl --root $INSTDIR\App\Cygwin\ --local-package-dir $INSTDIR\Data\Packages\ --packages desktop-file-utils python subversion wget'
!macroend[/code]
However, this didn't actually install those packages ... not sure why. However, I was able install the following packages through the package manager:
desktop-file-utils
shared-mime-info
Without encountering the error - which then allowed me to install other packages, specifically:
subversion
wget
And then I was able to install the cyg-apt: https://code.google.com/p/cyg-apt/
And now everything appears to be working as expected. Additionally, since I'm testing this on a box where cygwin is already installed and environment variables are configured for that environment, I modified Terminal.bat to remove the existing path data.
Hi there,
very well done !
I would absolutely love to install cygwin
and test it out thoroughly... and report back the results.
Please let me know where i can pick up tar/zip file from.
Best wishes
bob
You can find the link on top of this page.
For the record, current link is:
https://dl.dropbox.com/u/64204/CygwinPortable_1.7.17-1_Development_Test_...
Hi Thasmo,
I can see that this TEST_6 version was released on March 30th.
I can also see that others have announced (and fixed) an issue with updating cygwin with additional packages (4th & 5th of June).
So it appears that the TEST_6 version is no longer at the 'tip'
And .. When i installed the TEST_6 version i noticed that i had to download and use the setup.exe from cygwin.com (and then modify the ini file) rather than use the cygwinSetup.exe file provided in TEST_6 release. The cygwinSetup.exe file simply failed when i tried it, but the 1.7 setup.exe appeared to work cleanly when i tried it. Again, this lead me to wonder if TEST_6 is a previous version.. and no longer at the tip.
So this is why i was asking where i can download the new version from.
Naturally, i can road test TEST_6 (and report back my findings). But perhaps you'd prefer these efforts were invested in the tip version ?
Please let me know.
bob
PS. It's an excellent idea making cygwin portable.
Hi there!
I've updated the link above to the latest version - although I can not reproduce some of the mentioned problems.
Which ini file are you talking about? I've just uninstalled and installed Cygwin Portable again and I had no problems at all. The Installation Routine will download setup.exe from the Cygwin website and will execute it to install the base packages.
I'd be happy if you're willing to test out the latest release - but be sure to backup any existing Cygwin (Portable) installation just in case.
Please report back anything you find out. You can also use the issue tracker on Github: https://github.com/thasmo/portableapps.cygwin/issues
Thanks a lot for your help and feedback!
Hi Thasmo,
Thankyou.
I will install TEST_7 and try it out on a few different machines
and i will detail my findings .. and any fixes i apply.
Have a nice weekend.
bob
Very useful and work very well, I start using Cygwin Portable now, I will give feedback if I have some problem
Using:
*) CygwinPortable_1.7.20-1_Development_Test_7_English_online.paf.exe with unlimited access (virus protection COMODO triggers this dialog)
*) Windows 8 platform
*) installing into Dropbox folder with Dropbox syncing paused
*) Cygwin previously installed (update 1.7.20) in a different location (non-shared location)
Start installation. Downloads packages just fine.
While Installing, I get to:
"Installing",
"_autorebase-000359-1",
"/etc/postinstall/autorebase.bat"
At this point it appears to be stuck in a loop (last line flutters as if working/updating the text) and doesn't proceed past this point. After about 10 minutes of waiting, I "cancel". After which, of course, I am not installed properly.
I tried it with the natively installed Cygwin (twice) and then again after deleting the natively installed Cygwin with the same results.
Thoughts or (constructive) suggestions?
Mike
Newest version is 1.7.23 Test 9, but somehow the post install script doesn't trigger the cygwin setup anymore. It seems like this is because the cygwin setup required admin rights since some time now and the post install script can't launch the setup, it fails silently. Any ideas how to fix it?
I'm refering to this file: https://github.com/thasmo/portableapps.cygwin/blob/master/Other/Source/P...
Since you just updated the base app, shouldn't you restart your Dev Test numbering?
Ah, maybe - I'm not sure. I thought the numbering goes on until the app goes out of "testing", theoretically, no?
Yes, it stays in testing, but the numbering should change. See here for my thoughts, and those of a few others, on the matter: https://portableapps.com/node/28576
I installed Cygwin 1.7.23-1 Development Test 9 but trying to run it gaves me "... is not valid Win32 application" What can I do???
Hi
I've the same problem: when I start cygwin it stop with an error 'bout "App\Cygwin\bin\mintty.exe"
The problem is that there isn't a directory \bin under \Cygwin and so the terminal.bat can't start
someone can help?
thanks
IT specialist
Writing/book coach
Ghostwriter
Game creator
Probably CygwinPortable v1.7.23_Development_Test_9 runs only on 64bit Windows.
I was able to switch over to a computer running 64-bit Windows, so I was able to install Cygwin directly into the /CygwinPortable/App/Cygwin directory. But I may not always have a computer that runs this version of Windows. Where can I get hold of an earlier 32-bit version of CygwinPortable? I found the SourceForge site confusing, and couldn't get the file I downloaded from there to work.
You need to probably run \App\Cygwin\Cygwin.exe once to install Cygwin into the \App\Cygwin\ directory. This should run automatically when installing Cygwin Portable, but it's not working for Development Test 9, so you have to do it manually for now.
When I try to run this file on a Windows 7 machine, I get "The version of this file is not compatible with the version of Windows you're running"... is this version not Windows 7-compatible? Thanks for working on this, R.M.
Do you run 32bit Windows7?
Attempting to execute CygwinPortable_1.7.23_Development_Test_9_English_online.paf.exe
produces the following error during installation:
"The downloaded copy of Cygwin.exe is not valid and can not be installed. Please try installing again."
I've attempted to install multiple times with the same result. Installer dump:
Output folder: C:\Users\csandwith\Dropbox\PortableApps\CygwinPortable
Preparing to upgrade Cygwin Portable...
Create folder: C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded
Downloading Cygwin.exe...
Installing Cygwin Portable...
Rename: C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded\Cygwin.exe->C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded\Cygwin.exe
Create folder: C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded
Downloading Cygwin.exe...
Installing Cygwin Portable...
Rename: C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded\Cygwin.exe->C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded\Cygwin.exe
Delete file: C:\Users\CSANDW~1\AppData\Local\Temp\nscB32C.tmp\Downloaded\Cygwin.exe
The downloaded copy of Cygwin.exe is not valid and can not be installed. Please try installing again.
Cygwin.exe is not valid.
CygwinPortable_1.7.23_Development_Test_9_English_online.paf.exe have been tried with the same result on:
Win7 enterprise N 64bits
Win7 enterprise N 32bits
Win7 Pro 64bits
WinXp Pro 64bits
And on thoses Virtuals:
Win7 enterprise N 64bits, and 32bits
Win7 enterprise 64bits
Win7 family 32 and 64 bits.
So, how to test it please?
Is thasmo or project still alive, or completly dead?
Hi there!
Sorry for not being active lately. I think the problem is that the Portaple Apps Installer tries to download the Cygwin setup.exe file, but as Cygwin got some updates lately, the MD5 file hash doesn't correctly validate against the new setup.exe file.
Going to release an updated version in a second.
Updated to 1.7.25. Note that you have to run Cygwin.exe manually after installation for now - unfortunately I'm not able to get it running automatically.
With 1.7.25 I get same error on install: cygwin.exe is not valid
Cygwin Portable uses setup-x86_64.exe, so it probably won't run on 32bit operating systems. Maybe you got a 32bit OS?
No, i am using 64 bit Win7.
The error comes up on install.
I think it tries to download cygwin.exe etc. and stops right there because maybe hash value is wrong or something
I wonder why this package is "only for 64bit Windows". This is AFAIK the only portable software which is not able to run on 32bit.
BTW I often use 32bit Windows. What a pitty.
Same install issue as above on Windows 8 Professional x64.
Alright - this is so weird. Either I was too dumb to copy/paste the correct MD5 checksum to the installer.ini or the Cygwin installer file changed but the version did stay the same. I'm not sure. Anyway, I'll release Test 2 in a sec. Note that you still have to run the Cygwin.exe manually for now as I'm not able to get it triggered by the PortableApps installer.
Is it possible for you to create two different packages, one for each architecture (x86, x86_64)? This would aid the people who need x86 for older computers but would still allow the flexibility to download the right setup package like you do now.
Actually it would be cool to have the user decide while installing the app. Trying to get some info on that here: https://portableapps.com/node/38450
I meant two separate installers; one for each architecture. I don't know if there is a way to put the extra box in there without creating your own NSIS script for the installer...
Actually we don't need different installers for different platforms, we rather need a new launcher (or automagic switcher) after the installation while we run cygwin to pick the right cygwin.exe.
In the short term separate installers which work only on a specific platform would be fine enough. Thanks in advance.
32bit cygwin runs on a 64bit system but
64bit cygwin does not run on 32bit windows.
So IMHO you ought to compile the portable package rather for the 32bit version.
I'd love to implement a "manual switcher" while installing the app. The optimal solution would be to only show the choice if the setup runs on 64-bit Windows, if not, we don't need a switch.
Is it possible to implement something within the PortableApps installer?
Does the following help?
!include x64.nsh ${If} ${RunningX64}It would be awesome to have the user decide at the installation process, because someone still may prefer the 32bit version even if running on a 64bit OS. Also there's still some Cygwin packages which don't haven been ported to 64bit.
It's a portable app, so you it could be that you have a x86 and x64 system. Why don't let the system decide which one to use?
ProgramExecutable=cygwin.exe
ProgramExecutable64=cygwin64.exe
Your idea isn't wrong but why use x86 on a 64-bit system?
Ah, thank you - I didn't know that was possible. So, I still see a problem there, because Cygwin installs compiled packages and they're either 32bit or 64 bit, which means if you're on a 32bit PC and you install the 32bit version, all installed packages will be 32bit and if you then run Cygwin Portable on a 64bit PC, they installed packages won't run. Which means you probably would need to have 2 separate installations, which is kind of nonsense imho.
I didn't think of this aspect yet - however this may tells me that the *only* save way is to run the 32bit version, because it would run on 32 and 64bit systems.
Decisions! :>
Version 1.7.25 Development Test 3 released. Installation seems to be stable now.
-
I think terminal.bat and setup.sh need some love, but I'm not that experienced in using batch files and using mkpasswd and mkgroup. What would be the correct way to create a new user and does it make sense to override the user to 'root' for the portable version of Cygwin?
Feedback and oppinions on this is highly appreciated!
Is there an ETA for the 32bit Cygwin Portable?!
Some minutes ago.
Tested the x86 version. Works fine.
Thx thasmo!
Quick question. Sorry if I sound like a newbie but how do I add more packages into Cygwin? For example, "git"?
And great job on this development.
Do I manually install the packages into "CygwinPortable\App\Cygwin\bin"?
Thanks!
The default way is to use Cygwin's setup.exe to install/modify packages. In CygwinPortable that is 'App\Cygwin\Cygwin.exe'. You could also use a CLI package manager like 'apt-cyg' or 'cyg-apt', but they're no official programs. Additionally you can use/install packages from http://cygwinports.org/, they're great - e.g. you get a newer version of Git.
You *can* copy/paste *some* programs into 'App\Cygwin\usr\local\bin', but they need to support Cygwin, otherwise they won't work properly.
E.g. node.exe (from http://nodejs.org/) will not work with Cygwin.
I use the packer-*.exe (http://packer.io/) files inside 'App\Cygwin\usr\local\bin' and this works well because Packer supports Cygwin.
No clue why this is.. Maybe the installer forgot to install it? Did I miss a step? I read all the comments and didn't see anyone else with this problem. I have cygwin on my home pc which works well. And I tried this on all three pcs I have here. One runs Vista, the other XP, and the laptop Windows 8.1. All of them have this issue.
Hey there! I tried to test and reproduce what you describe but wasn't able to, unfortunately. When installing the 64bit or the 32bit version, the PortableApps installer should download the setup.exe from Cygwin which then installs all base packages including mintty.exe. I do not have a local Cygwin installation (except the portable one); maybe that's the reason for the installer not downloading the correct base packages?! Would it be possible for you to test the installer on a machine which does not have Cygwin installed already? Thanks!
And windows 8.1, Same thing. Also I noticed that it installs everything to another folder named E:\ PortableApps. I watched the installer, it seems to download alot of packages, but I didn't see anything mentioning Mintty anywhere.
I just ran the config shortcut on PortableApps Platform and.. It points to E:\PortableApps, and on the list, it shows mintty installed. So... maybe the shortcuts made on the portableapps platform are pointing to the wrong folder?? It would help if I could see the paths that the shortcuts are set to. Right clicking on it and then Explorer Here don't help much.
EDIT: ok so yea the Shortcut created is pointing to the wrong directory. It should be Pointing to E:\PortableApps\Bin\mintty.exe. Least I found it in there.
That's weird. The full path should actually be PortableApps\CygwinPortable\App\Cygwin\bin\mintty.exe - did you try the installation on a machine where Cygwin (not the portable version) has not been installed already?
And it does the same exact thing. I have no clue why it installs where it wants to. I can't change the paths it installs to when I first install it so yea...
I wonder what does PortableApps.com founder, John T Haller think of all of this? This one is definitely a worthwhile project.
Hi,
Is there any progress about this app?
thank you
Currently I'm not working on it but at it's current state the app should kinda work, I believe. Do you miss anything?
If the app will not be on market (app list) I can not use it. Thank you for your interest.