VS2010 poco Beaglebone Cross Compile. Build fail Header file not found

Sysprogs forums Forums VisualGDB VS2010 poco Beaglebone Cross Compile. Build fail Header file not found

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #7456
    dhruv_acharya
    Participant

    I am very much new to visual studio, c++, poco and visualGDB.

    I have extracted poco libraries to C:\poco-1.6.1. I am trying very basic poco “hello, world” as you can see in image I have included #include <Poco/String.h> But when I build, it says that no such header file. As you can see I have also provided path for Include directories and Library Directories. Please Guide me for successfully compile this locally and remote debug it on Beaglebone.

    PS: Please use this link if you can not see the image. Sorry.

    • This topic was modified 8 years, 10 months ago by dhruv_acharya.
    #7461
    support
    Keymaster

    Hi,

    Please right-click on your project in Solution Explorer, select “VisualGDB Project Properties”, go to the Makefile Settings page and add the include directories there.

    Let us know if you run into further problems.

    #7462
    dhruv_acharya
    Participant

    Hi Bazis,

    Thanks for the help. But, after I add this directory path to makefile setting page, error for no such header file is gone, but now it gives following errors:

    Error    1    error VGDB1000: undefined reference to `Poco::Ascii::CHARACTER_PROPERTIES’    C:\poco-1.6.1\Foundation\include\Poco\Ascii.h    129    1    Test_Poco
    Error    2    error VGDB1000: undefined reference to `Poco::Ascii::CHARACTER_PROPERTIES’    C:\poco-1.6.1\Foundation\include\Poco\Ascii.h    129    1    Test_Poco

    You can see the this image for more reference.

    #7472
    support
    Keymaster

    Hi,

    This means that you are missing the reference to the static library (should be called libPoco.a or something similar). Note that if you have just downloaded the sources from Internet, you need to configure and build the library according to the instructions provided by its vendor. This will produce the .a file that you can reference from VisualGDB Project Properties (normally add the directory with the .a files to the Library Directories and add the library name without the ‘lib’ prefix to the Additional Libraries).

    #7546
    dhruv_acharya
    Participant

    Hi,

    Yes I think you are right. I have solved problem via this:

    1. I have installed the official poco per-built libraries from debian source on my beaglebone using sudo apt-get install libpoco-dev.

    2. Created a new project and sync all the system root headers and library.

    3. Success.

     

    #7560
    support
    Keymaster

    Good to know it works. If you run into further problems, let us know.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.