SDK build environment

I just realized dazstudio SDK is outdated.
i finally found and installed visualstudio 2010.(Service Pack 1)
installed Qt 4.8.7 (32 Bit) I can't find 64 bit!
but still I should find old version of the Cmake that supports VS 2010
I installed all, but windows 7 sdk! I can't!
everything supre outdated (14 years!)
did I missed something? any solution?
someone can tell me structure to build a correct pipeline?
My target Daz version is 4.23 (64 bit) , Can we make 64 bit plugins at all?

Post edited by MehdiZangenehBar on

Comments

  • Yea, but links are broken, and I still don't get my questions...

  • MehdiZangenehBar said:

    I just realized dazstudio SDK is outdated.
    i finally found and installed visualstudio 2010.(Service Pack 1)
    installed Qt 4.8.7 (32 Bit) I can't find 64 bit!
    but still I should find old version of the Cmake that supports VS 2010
    I installed all, but windows 7 sdk! I can't!
    everything supre outdated (14 years!)
    did I missed something? any solution?
    someone can tell me structure to build a correct pipeline?
    My target Daz version is 4.23 (64 bit) , Can we make 64 bit plugins at all?

    Of course you can. If your bin and lib directories don't have x64 subdirectories, then there's something wrong with your SDK install.

    The SDK is outdated, but the header files are such that you can compile and link against the latest DS libs.

    There is no 32/64 bit version of Qt; it will be whatever you compile it for, which makes me think you might simply not have selected x64 as the architecture.

    And I would just skip cmake altogether and just build up your project from the ground up as a Windows DLL project. It's kind of a pain adding the build tool rules for uic and moc, but if you know how to build a Qt app in general, you'll know what to do.

    This is becoming strange... I am not an experienced Win32 developer and don't know what I'm doing, but did get VS2022 working, while others have expressed having difficulty. I think I probably made mistakes that somehow offset each other.

    In any case, the SDK being old is not an issue as it would appear to be, and you can do what you are trying to do.

     

  • OK, my new update:
    SDK have 64 bit for sure.
    Daz Studio is 64 Bit.
    Visual Studio 2010 express installed SP1 (Toolset 100)
    ​Windows 7 SDK already exist in VS 2010 folders.
    Cmake 3.24 installed, instead of the latest version : cmake_minimum_required(VERSION 3.4...3.24) and it works perfectly.
    The ONLY problem is Qt 4.8.7 64 bit is not exist, we have to build it from the source... (I wish someone have the builded and send me the link)
    I just tried 32 bit for test and plugin is created , but not loaded in DazStudio, (Help > About installed plugins, shows Plugin failed to load!)

  • surrealsurreal Posts: 173
    edited February 19

    MehdiZangenehBar said:

    installed Qt 4.8.7 (32 Bit) I can't find 64 bit!

    Are you saying that you only have the DAZStudio4.5+ SDK/bin/Win32 folder and do not have the DAZStudio4.5+ SDK/bin/x64 folder?

    Did you follow all the steps in the "Compiling DAZ Studio Plugins on Windows" section of the SDK documentation?

    It describes how to setup for building 64 bit.

    If you have built a 32bit plugin then I can understand you getting a "Plugin Failed to load" error. I think the 32bit is a carry over from when there was a 32bit version of DAZStudio.

    You will need to build x64 plugins for the current DazStudio.

    If you still get an error after building a 64bit plugin, have a look in your Daz Studio log file(Help > Troubleshooting > View Log File).

    It is always a good starting point for debugging errors. The alternative is to use VS debugging and connect to DazStudio after it starts and before it tries to load your plugin.

    I can understand TheMysteryIsThePoint appreciation of VS2022 and dislike of cmake. Myself I much prefer using cmake(when adding a new project) and VS2017. I find that VS2022 will occationally break a project and the simplest solution is to open and build the project in VS2107, most probably because I know VS2017 better than VS2022.

    Post edited by surreal on
  • To compile for 64 bit DS you need to select that option in Cmake.

    DS 32 still exists.

     

  • MehdiZangenehBar said:

    OK, my new update:
    SDK have 64 bit for sure.
    Daz Studio is 64 Bit.
    Visual Studio 2010 express installed SP1 (Toolset 100)
    ​Windows 7 SDK already exist in VS 2010 folders.
    Cmake 3.24 installed, instead of the latest version : cmake_minimum_required(VERSION 3.4...3.24) and it works perfectly.
    The ONLY problem is Qt 4.8.7 64 bit is not exist, we have to build it from the source... (I wish someone have the builded and send me the link)
    I just tried 32 bit for test and plugin is created , but not loaded in DazStudio, (Help > About installed plugins, shows Plugin failed to load!)

    You don't need to compile it. You've got the DLLs and LIBs already. You just need the headers.

    Again, there is no separate 32 or 64 bit release of Qt 4.8.7; it will be for the architecture for which it was compiled.

    You want this one.

    If you are getting 32 bit build artifacts, it is because that's what you asked for. Set it to x64/Release.

     

  • Aha, thanks guys, Yes my target is 64bit. (I don't want 32 bit at all)
    Thanks for the Qt, it seems I though wrong, I should reference that from SDK, no need to install separate Qt.
    I am struggling with the windows 7 SDK (both online and iso installer), I got error that SDK needs dotnet framework in order to install correctly, I just installed and re installed .Net several times, but still got error.
    I guess if I find VisualStudio 2010 professional, I don't have to install windows 7 SDK right?

  • OmnifluxOmniflux Posts: 386

    MehdiZangenehBar said:

    I am struggling with the windows 7 SDK (both online and iso installer), I got error that SDK needs dotnet framework in order to install correctly, I just installed and re installed .Net several times, but still got error.

    I recall having some difficulty the last time I installed this SDK.

    I have these two links bookmarked, one of which I think helped me resolve the issue.

    Also, there are some instances in which you should NOT install "Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1" after installing the SDK, but I cannot remember what they are...

Sign In or Register to comment.