Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 28 Mar 2004 16:58:25 -0800 From: Lester Ingber To: cygwin AT cygwin DOT com Subject: request for some path advice Message-ID: <20040329005825.GA1084@ingber.com> Reply-To: Lester Ingber Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i I have a C project that I can compile and run fine using gcc, with or without -mno-cygwin. I have the I/O files in another directory, with the relative paths named in some .c files. When I use the -mno-cygwin option, I see I cannot use soft links for any IO directories, but I also cannot use the executable in another directory with the same relative path to the IO directory? So, under a ${PROJECT_PATH}/ I have SRC/ IO/ RUN/ Let's say I compile the code under SRC/. If I put the executable under RUN I get an access violation -- only under -mno-cygwin. If I keep the executable unde SRC/, it works OK. Is there any way of declaring my paths in my .c files to avoid these problems? Thanks. Lester -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/