On Thursday, 26 May 2016 at 15:41:45 UTC, TheDGuy wrote:
On Thursday, 26 May 2016 at 15:21:40 UTC, Basile B. wrote:
Use Coedit: the widget "library manager" allow to register
libraries in a single click and then they are usable on the
fly, in the projects or in a runnable modules, without
specifying anything (except a (*) in a project setting called
"libraryAliases".
https://github.com/BBasile/Coedit/wiki#library-manager-widget
It was especially designed because the other IDE suck a bit
with static libraries.
Thanks for the tip. I downloaded the version for windows from
github and it works fine so far but if i want to "run compiled
file" i get the message 'the executino of a runnable module has
been implicitly aborted" even though i can run the .exe file
manually without any errors. Do you know how i can run my app
from out of coedit?
Yes and no
- CE Projects and DUB projects are always run outside (by
deafault)
- runnable modules can be run outside using: "Compile file and
run outside".
It's because runnable modules are different from projects. They
are usually compiled so fast that you can recompile before each
execution but you can open a GH issue and ask for a new action
"run compiled file outside" (to split the action in two phases)
When they are run inside, you can use the "Input process" widget
to pass some input to the process that's hosted (see the
"Windows" menu).
To register a DUB package, you can either fetch (DUB icon) or
clone the repo, open the DUB JSON project, compile the right
config, then in the libman there's a icon with a gray chain over
a book. Click this icon and the library is registered.
Note that DUB projects are displayed in another widget that the
one displayed by default at the right (see "DUB project editor")
in the "Windows" menu.
