From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: running .bat file in cygwin
Date: Wed, 11 Jul 2012 18:25:00 -0000 [thread overview]
Message-ID: <CA+sc5mnv_n=_9oE=qgZ5Hy2hz8QkzxLVviqPvkCM3pqObguV5g@mail.gmail.com> (raw)
In-Reply-To: <34146666.post@talk.nabble.com>
On Wed, Jul 11, 2012 at 12:26 PM, emon wrote:
>
> Dear All,
> I am a newbie in cygwin. However, I have used mingw so far,
> but it is not supporting fork(), so I need to switch to cygwin. I have
> created a build.bat file in my mingw (programming language C):
>
Note, fork requires the cygwin1.dll file. Are you prepared for that?
> gcc -o mask mask.c -pg -I/c/opencv/build/include -lopencv_core231
> -lopencv_highgui231 -lopencv_imgproc231 -L. -L/c/opencv/build/x86/mingw/lib
>
> Can anyone suggest me how I can run this .bat file at cygwin or refer me to
> a site.
I've read all the other response, etc. However, if you want to use
the .bat file you can do
cmd /c build.bat
take care that your PATH has all you need and note that /posix/paths
don't 't work with MinGW gcc. But since you need fork() you'll need
to use the Cygwin GCC anyway.
--
Earnie
-- https://sites.google.com/site/earnieboyd
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-11 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:26 emon
2012-07-11 16:38 ` Adam Dinwoodie
2012-07-11 16:39 ` Larry Hall (Cygwin)
2012-07-11 17:05 ` emon
2012-07-11 17:54 ` Larry Hall (Cygwin)
2012-07-11 16:59 ` Greg Chicares
2012-07-11 18:25 ` Earnie Boyd [this message]
2012-07-11 19:33 ` emon
2012-07-11 19:41 ` James Johnston
2012-07-12 2:57 ` Earnie Boyd
2012-07-12 19:52 ` emon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+sc5mnv_n=_9oE=qgZ5Hy2hz8QkzxLVviqPvkCM3pqObguV5g@mail.gmail.com' \
--to=earnie@users.sourceforge.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).