Getting started

Great! Thanks for checking it!

Dear @Oliver , We expect it to be fixed in a few weeks.

Thank you.I will contact.

Thank you so much for helping me. I tried to link exactly Qt5.12.5 (my own version is 5.14.1) so it works now. Again, thank you so much. Best regards, Dong.

Hi, Sorry for the issue the file was not shipped with the SDK. See : https://documentation.samson-connect.net/developers/latest/page_installation.html To launch SAMSON just execute SAMSON-Core after doing the step inside the previous link. If the file is absent you can create SAMSON-Core.command with the following content #!/bin/sh echo "saving context" SAVED_DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH SAVED_DYLD_FRAMEWORK_PATH=$DYLD_FRAMEWORK_PATH SAVED_DYLD_FALLBACK_LIBRARY_PATH=$DYLD_FALLBACK_LIBRARY_PATH echo "launching SAMSON-Core" script_dir=$(cd "$(dirname "$0")";pwd) cd "$script_dir" echo "You need to add ~/Qt5.12.5/5.12.5/clang_64/lib folder in your DYLD_FRAMEWORK_PATH or edit this file" #export DYLD_FRAMEWORK_PATH=~/Qt5.12.5/5.12.5/clang_64/lib or the one corresponding to your setup export DYLD_LIBRARY_PATH=$script_dir export DYLD_FALLBACK_LIBRARY_PATH=$script_dir ./SAMSON-Core #available flags --disablenetwork /--import /--logconsole /--logfile "file" /--logdefaultfile echo "restoring context" export DYLD_LIBRARY_PATH=$SAVED_DYLD_LIBRARY_PATH export DYLD_FRAMEWORK_PATH=$SAVED_DYLD_FRAMEWORK_PATH export DYLD_FALLBACK_LIBRARY_PATH=$SAVED_DYLD_FALLBACK_LIBRARY_PATH then execute chmod +x SAMSON-Core.command then execute chmod +x SAMSON-Core Jocelyn

@emmanuel Ok, maybe the "Get the SDK" button is not clear. How to download SAMSON SDK is explained at the end of the page you mention first : https://documentation.samson-connect.net/developers/latest/page_installation.html#SDKInstallationStepsDownloadingSDK Sorry for the issue. Jocelyn

@elisa A common problem due to Windows being case-insensitive. :)

Dear @Jean-Baptiste , Thank you for your interest in SAMSON! According to your screenshot, I think the problem here is due to an unnecessary newline character in the command you past in the PowerShell terminal due to copying. Please, note: we recommend not to build your Elements in the SAMSON Debug folders - you should use a dedicated folder to develop your SAMSON Elements If you have -DQT5_CMAKE_INCLUDE_DIR environment variable defined in your system you can compile for Visual Studio 2017 like this: cmake -DSAMSON_SDK_PATH="C:\Program Files\NANO-D\SDK\0.7.0" -G"Visual Studio 15 Win64" .. else like this: cmake -DSAMSON_SDK_PATH="C:\Program Files\NANO-D\SDK\0.7.0" -G"Visual Studio 15 Win64" -DQT5_CMAKE_INCLUDE_DIR="C:\Qt\5.9.3\msvc2017_64\lib\cmake" .. You can copy the command from here. You can also check whether the cmake is defined in your system by e.g. checking its version number: cmake --version I would also recommend to follow the updated tutorial on Building on Windows in the Developer guide.

Hi Dmitriy, My CMakeLists for the Python Bindings version is like you posted above, so I'm not linking in the debug mode. My other branches don't have any reference to Python in the CMakeLists, so they are not linking neither.

Thanks, SAMSON SDK 7 works properly, but v6 still not (I've checked all requirements and followed installation steps from the instruction). Still, I've got working version of SDK, so thank you again)

Good luck @Laëtitia ! You can check https://github.com/1A-OneAngstrom/SAMSON-Developer-Tutorials/tree/develop for some SAMSON Elements Samples. We will be adding more soon. Feel free to ask questions!

Great! You can check the tutorial on building a SAMSON Element on Linux. Feel free to ask questions if you experience any problems! Best, Dmitriy Marin

I thought I did but you're right now it's fine. Thanks!

In case someone else is in the same situation. I just finished porting our plugin to 0.7.0 and the only changes I had to make were in SAMSON::getProxy (the arguments have changed), and the call functions of the proxies (arguments of SBValue type used to be pointers, now they are passed by reference). We have still to test it to make sure all functionality is working, but so far it seems that was it. Regards, Elisa

Yes thanks. That's what I was looking for.