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





  • Posts   Search Threads
  • ahjuNovember 23, 2008 3: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 3: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 1: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

16,377 users have contributed to 46,364 threads and 164,041 posts to date.

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

In the past 3 days, the most popular thread for everyone has been Program compiles in release but not debug The most posts were made to You need to show us the whole The post with the most views is vectorization of sin/cos results in wrong values

Please welcome our newest member fruitbrown


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