cabal

Stop command prompt from opening when running exe file built from haskell project

社会主义新天地 提交于 2020-12-12 09:39:30
问题 I have created a small application that uses the gloss library for a GUI. When typing "cabal run [cabal file]" the project is built and run, and only prompts the GUI. When I instead go and click on the .exe file that was generated from the build, the GUI opens but so does the command prompt. I want to stop the command prompt from opening and only have the window from gloss open. 回答1: By default on Windows GHC builds console programs, which open a Command Prompt terminal if one isn’t open

Stop command prompt from opening when running exe file built from haskell project

浪子不回头ぞ 提交于 2020-12-12 09:39:10
问题 I have created a small application that uses the gloss library for a GUI. When typing "cabal run [cabal file]" the project is built and run, and only prompts the GUI. When I instead go and click on the .exe file that was generated from the build, the GUI opens but so does the command prompt. I want to stop the command prompt from opening and only have the window from gloss open. 回答1: By default on Windows GHC builds console programs, which open a Command Prompt terminal if one isn’t open

Stop command prompt from opening when running exe file built from haskell project

旧街凉风 提交于 2020-12-12 09:38:05
问题 I have created a small application that uses the gloss library for a GUI. When typing "cabal run [cabal file]" the project is built and run, and only prompts the GUI. When I instead go and click on the .exe file that was generated from the build, the GUI opens but so does the command prompt. I want to stop the command prompt from opening and only have the window from gloss open. 回答1: By default on Windows GHC builds console programs, which open a Command Prompt terminal if one isn’t open

Haskell Cabal package - can't find Paths_ module

只谈情不闲聊 提交于 2020-12-02 07:28:12
问题 I'm working on a Haskell project (Happstack server + Blaze HTML/front-end as main libraries) and I want to add a static data directory. Looks like you can do so with Cabal using the auto-generated Path_<package_name> module. So in my example, the package is called new-website , so that module should be called Paths_new_website . Link to Cabal docs re: a custom package's Paths_pkgname module. From the command line and using cabal repl , I am trying to confirm that I'll have access to the Paths