WIP: init nidaqmx #74980
WIP: init nidaqmx #74980
Conversation
| @@ -0,0 +1,392 @@ | |||
| /nix/store/6j558vkwvk1a15ihgglniiwxwjfwj5mh-libiotracelog-foo/lib/x86_64-linux-gnu/ni-iotrace/lib64/libNiSpyLog.so.18.1.0 | |||
There was a problem hiding this comment.
This file will be removed..
| repo = lib.importJSON ./repo.json; | ||
|
|
||
| # Add symbolic links to versioned .so files. | ||
| addSharedObjectVersioningLinksHook = writeShellScript "add-shared-object-versioning-links" '' |
FRidh
force-pushed
the
nidaqmx
branch
2 times, most recently
from
889d3f9
to
57be0e6
Compare
This commit adds the NI-DAQmx software for data-acquisition with NI hardware. The nidaqmxbase package is small, however, provides functionality only for a limited set of hardware. The nidaqmx package on the other hand supports (nearly) all hardware. Packages are provided however only for Windows and CentOS. The RPM repo data is used to generate a package set. TODO: - [ ] split nidaqmx, nixdaqmxbase and nidaqmx-python in separate commits - [ ] nidaqmx-python should optionally work with nidaqmx and/or nidaqmxbase - [ ] fix kernel/dkms packages. Probably need to set KBUILD_EXTRA_SYMBOLS - [ ] provide nixos module and mapping modules/packages
|
Hello, I'm a bot and I thank you in the name of the community for your contributions. Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do: If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list. If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past. If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments. Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel. |
stale
bot
added
the
2.status: stale
This commit adds the NI-DAQmx software for data-acquisition with NI hardware.
The nidaqmxbase package is small, however, provides functionality only for a limited set of hardware.
The nidaqmx package on the other hand supports (nearly) all hardware. Packages are provided however
only for Windows and CentOS. The RPM repo data is used to generate a package set.
TODO:
Motivation for this change
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"./result/bin/)nix path-info -Sbefore and after)Notify maintainers
cc @