Loading...
You are not logged-in Login/Register





  • Posts   Search Threads
  • ahjuNovember 23, 2008 2:20 AM PST   
    SDK RemoteControl Sample missing StatusStringsD.lib

    Hi,

    I execute the RemoteControlSample in the SDK4.0, but I get the following error:

    Error 1 fatal error LNK1104: cannot open file 'StatusStringsD.lib' .

    I have searched in the SDK folder and cannot found the StatusStringsD.lib.

    Isn't the lib in the SDK?

    And the readme.txt shows complie the StatusString sample in debug will build the StatusStringsD.lib, but I cann't find the StatusString sample in the SDK.

    Thanks.



    Sreelekshmy Syamalakumari (Intel)November 24, 2008 2:38 PM PST
    Rate
     
    		 #1
    Re: SDK RemoteControl Sample missing StatusStringsD.lib

    Hi,

    StatusStringsD.lib is not included in the sdk. For getting this, you have to  compile the StatusStrings library in Debug mode. This is located in the sdkwindowscommonstatusStrings folder.

    Let us know if you have any further questions.

    Thanks,

    Sree

     



    ahjuNovember 26, 2008 12:18 AM PST
    Rate
     
    		 #2 Reply To #1
    Re: SDK RemoteControl Sample missing StatusStringsD.lib

     

    Hi,

    StatusStringsD.lib is not included in the sdk. For getting this, you have to  compile the StatusStrings library in Debug mode. This is located in the sdkwindowscommonstatusStrings folder.

    Let us know if you have any further questions.

    Thanks,

    Sree

     

    I got it, thanks!



Forum jump:  

Intel Software Network Forums Statistics

17,025 users have contributed to 48,317 threads and 172,754 posts to date.

In the past 24 hours, we have 9 new thread(s) 56 new posts(s), and 52 new user(s).

In the past 3 days, the most popular thread for everyone has been How to manage rounding by IVF ?? The most posts were made to Most likely, the issue is that The post with the most views is Optimalization of sine function\'s taylor expansion

Please welcome our newest member redfruit83


For more complete information about compiler optimizations, see our Optimization Notice.