Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Seismic DMS-Deprecated
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe Software
  • Platform
  • Domain Data Mgmt Services
  • Seismic
  • Seismic DMS-Deprecated
  • Issues
  • #4

Closed
Open
Created Dec 02, 2020 by Walter D@dsouzawalterMaintainer

The output of SDAPI build are DLL files. Where and how do we reference them?

The SDAPI RELEASE build is creating the following files:

  1. cpprest_2_10.dll
  2. jsoncpp.dll
  3. jsoncpp.pdb
  4. jsoncpp_static.lib
  5. libcurl.dll
  6. sdapi.dll
  7. sdapi.exp
  8. sdapi.lib
  9. sdapi.pdb
  10. sdapi_static.lib
  11. wastorage.dll
  12. zlib1.dll

Since there is no EXE file generated, it is not clear which code will be calling the above files. If it is the SDUTIL calling these DLL files, the python code does not have ctypes to call them.

Edited Dec 03, 2020 by Walter D
Assignee
Assign to
Time tracking