Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Nicolas Bigaouette
@nbigaouette
blob
;)
as you said, you never know, it's often small details that you forget to set properly...
Nathan Dwek
@nathdwek
Well I don't have really any idea
except two things
mmmh actually more like zero things
Yeah I'm sorry
Nicolas Bigaouette
@nbigaouette
ahha
:P
Nathan Dwek
@nathdwek
I was going to say using calling a shell to call make could lead to bizarre stuff, and running linking after compilation could make it discard error for previous target
but both are stupid
did you give build-make a try?
Nicolas Bigaouette
@nbigaouette
yes, but it freezes atom. The thing is 1) I don't use a makefile, I use cmake, 2) the repo this is run on contains a lot more than just the code, so there is no makefile in the root directory. My goal was to setup multiple 'targets' (selectable through F7). I run cmake once (per subproject) in their respective build directories, select which subproject to build using F7, and build it...
Nathan Dwek
@nathdwek
I won't make you the insult of asking if you considered build-cmake
I guess I'm all out of options :s
sorry for losing your time
Nicolas Bigaouette
@nbigaouette
I'll take any suggestiongs, there is no stupid one
well maybe asking to reboot would be a stupid one... :P
Nathan Dwek
@nathdwek
Nah I'm sorry I think I'll just go to bed
If anyone please could tell me whether this package interacts with the gutter plz plz
That would make my mind a little saner
Alexander Olsson
@noseglid
Hi. I haven't read all of your conversation yet, but build doesn't directly interact with the gutter. However, it integrates with atom-linter which does. The matched errors are sent to the linter
Nathan Dwek
@nathdwek
Hi @noseglid , thanks for answering. Still wondering if a basic (correct) setup with build + provider + linter should display stuff in the gutter? It doesn't on my setup, it doesn't look like it does in the gif in the readme (build + build-make + linter it seems, same as my current config), and I can't figure what could be going wrong if it were supposed to
Alexander Olsson
@noseglid
Are you getting any matches on your regard? I.e. is the linter displaying errors?
Nathan Dwek
@nathdwek
Yup
Just like in the gif in the readme
Severen Redwood
@severen
I'm using atom-build and atom-build-cargo, whenever I try to build my project this red error pops up: emitter.prependListener is not a function.
It doesn't show up in the debug console
Alexander Olsson
@noseglid
@oli-obk Any issues publishing a new release for the Cargo provider?
Jan T. Sott
@idleberg
should it be encouraged to use a tag for build providers in package.json, e.g. build-provider?
Jan T. Sott
@idleberg
more obscure build providers incoming :smile:
Oliver Schneider
@oli-obk
@noseglid nope, publishing works great now
I accidentally published to npm first though xD needed to unpublish that
Alexander Olsson
@noseglid
@oli-obk awesome!
zzzgit
@zzzgit
hello friends
do you think that the documentation is too simple for new users?
i think i can't get anything about the usage of atom-build and related other plugins after finished reading the documentation
Nathan Dwek
@nathdwek
Hej, @noseglid would it be possible to review my pull request re:recursive Makefiles on atom-build-make?
Jan T. Sott
@idleberg
i added config to one of my providers and used atom.config.get() inside settings(). this seems to be called only once, even when i refresh the targets. is there anything i can do?
think of: user lauches atom, setting() gets called once. user edits the config, but the changes won't be read a second time. i tried preBuild(), but without success
Jan T. Sott
@idleberg
found the answer
Alexander Olsson
@noseglid
Emitting refresh from your provider will get the settings read again. You could do this when the configuration changes (as detected with atom.config.observe
Jan T. Sott
@idleberg
thanks, i found the answer in your makefile provider
:thumbsup:
Ben Creasy
@jcrben
folllowing up on my question at https://github.com/noseglid/atom-build/issues/261#issuecomment-255669937 - I'm working on command-line programs (basically just exploring C) and I'd like to be able to be able to build and run my small programs from Atom without switching to the terminal. Is that possible with this tool?
Basically it would work like this: I hit the build keyboard shortcut and then a dialog box pops up through which I provide additional arguments
Trent Schafer
@tschf
Is there any mechanism with the provider API to run multiple targets programatically? E.g. if I want to implement some workflow, so I can say.. run target 1, if success, run target 2, etc, or, even taking it a step further, and running a different target against a different file that the active tab
Trent Schafer
@tschf
I suppose for this to work, I would need to be able to both set the active target (I couldn't see this being possible with the command dispatch API with the currently exposed commands) and pass in to the build which file should be run.. If setting the active target is possible, I suppose too that the build output will be only for the last build, Ideally it could collate the outputs.
Oliver Schneider
@oli-obk
@tschf nope, this has been requested before, but has been declined. atom-build just provides the targets
Trent Schafer
@tschf
@oli-obk Ah, no probs! Thanks for letting us know.