Hello Guy,
>> I’m in the process of upgrading an 1.10 environment into the 2.0 century
> Skipping 1.12 entirely
Yes. 1.10 was good enough and there wasn't any time available to dive deeper to
determine the required modifications between 1.10 and 1.12.
I had added it to Makefile.common, I
Hello Graham,
> If using CMake, the new source file should be added to epan\CMakeLists.txt,
> probably in the list LIBWIRESHARK_FILES. If using nmake, then
> epan\Makefile.common is probably the right spot. More ifnormation on your
> changes would help.
epan/CMakeLists.txt was the right
On Feb 23, 2016, at 9:25 PM, Edwin Groothuis
wrote:
> I’m in the process of upgrading an 1.10 environment into the 2.0 century
Skipping 1.12 entirely
> and run in one last problem: The functions from a new file in epan/ don’t get
> recognized by the linker
On 24 February 2016 at 05:25, Edwin Groothuis
wrote:
> Greetings,
>
>
>
> I’m in the process of upgrading an 1.10 environment into the 2.0 century
> and run in one last problem: The functions from a new file in epan/ don’t
> get recognized by the linker for VS2013.
On 24-02-2016 05:25, Edwin Groothuis wrote:
Greetings,
I’m in the process of upgrading an 1.10 environment into the 2.0 century
and run in one last problem: The functions from a new file in epan/
don’t get recognized by the linker for VS2013. I have added it to
Makefile.common, the include
Hi
Could you provide some form of linker output so that we could see, which
functions you are talking about?
regards
Roland
On Wed, Feb 24, 2016 at 6:25 AM, Edwin Groothuis <
edwin.grooth...@riverbed.com> wrote:
> Greetings,
>
>
>
> I’m in the process of upgrading an 1.10 environment into the
Greetings,
I'm in the process of upgrading an 1.10 environment into the 2.0 century and
run in one last problem: The functions from a new file in epan/ don't get
recognized by the linker for VS2013. I have added it to Makefile.common, the
include file contains the WS_DLL_PUBLIC declaration. In