What does your plugin's CFLAGS look like in Makefile.nmake? And where are your header files that you're trying to #include? - Chris
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy O'Brien Sent: Tuesday, April 27, 2010 10:31 AM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in Windows Also, I can't seem to use relative paths for #include either. What gives? On Tue, Apr 27, 2010 at 09:44, Jeremy O'Brien <[email protected]> wrote: > Yeah I tried changing it to "\" and "\\", neither of which worked. :( > > On Sun, Apr 25, 2010 at 14:43, Maynard, Chris > <[email protected]> wrote: >> Just a guess, but maybe it's due to the different path separator ... i.e., >> '/' for *nix vs. '\' for Windows? >> - Chris >> ________________________________________ >> From: [email protected] >> [[email protected]] On Behalf Of Jeremy O'Brien >> [[email protected]] >> Sent: Friday, April 23, 2010 10:14 AM >> To: Developer support list for Wireshark >> Subject: [Wireshark-dev] DISSECTOR_SUPPORT_SRC in another directory in >> Windows >> >> I'm using DISSECTOR_SUPPORT_SRC in my Makefile.common to compile a c >> file in another directory that gets linked into my plugin. This works >> fine in linux, however in windows it gives a "cannot open input file >> ../common/support_file.obj" I moved the file to the same directory as >> my plugin, replaced the DISSECTOR_SUPPORT_SRC entry appropriately, and >> it compiled fine. So my question is, is it possible to have a plugin >> use a file that is not in the current directory for >> DISSECTOR_SUPPORT_SRC? >> >> My DISSECTOR_SUPPORT_SRC line just looks like this: >> >> DISSECTOR_SUPPORT_SRC = ../common/support_file.c >> >> Thank you, >> Jeremy CONFIDENTIALITY NOTICE: The contents of this email are confidential and for the exclusive use of the intended recipient. If you receive this email in error, please delete it from your system immediately and notify us either by email, telephone or fax. You should not copy, forward, or otherwise disclose the content of the email. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
